Que es?
The Weblog of Brett Singer. Bringing the world what it needs most - a blog.
Note: Sorry about all of the 'hot deals' entries (someone referred to this blog as
CorporateShill.com).
The deals and things are being fed into Multineedia.com. We will
soon move the deals category over to Multineedia so you don't have to read it, and we apologize for any inconvenience.
| September 2010 | ||||||
|---|---|---|---|---|---|---|
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 | ||
Subscribe
Subscribe to a syndicated feed of this weblog,
brought to you by the wonders of RSS.
Other blogs
Reading:
Great free software:
Thu, 03 Nov 2005
Quick Rant about browser crashing scripts and applets
Lately I have encountered a lot of web pages with elements that crash my browser of choice, which is Firefox. The biggest culprits are sports sites, such as NFL.com or CBS Sportsline. These pages tend to have a lot of multimedia elements, specifically Flash and other embedded videos. The most crash-prone seem to be MS-based protocols, but that's not a scientific observation.
It's not limited to the big guys, though. I was just on a small-ish site and tried to use the Check Spelling button on a forum post. Within seconds, Firefox crashed, the little error reporting window popped up, and the pages I was looking at were history (and not stored in the browser history). Why is this? Is it bad code? Is Firefox just too buggy for prime-time? As much as I hate (HATE) Internet Explorer for all of the ills it has foisted on the world, it does tend to render these bad pages better. Obviously this is because site designers are targeting IE users, which are plentiful. But is it really that hard to test your code on Firefox, which is becoming more and more popular (9.7% on the BBC's website, for example)? Do the site owners know that this is even happening? Maybe notifying the Firefox people (via the error tracking pop-up) isn't sufficient. Could the error tracker somehow connect to a whois lookup and then email the admin/technical contact for the domain where the site crashed? Easier said than done I'm sure, but my point is that Firefox shouldn't be trying to make itself work with every site that is poorly coded, badly designed, and/or annoyingly full of embedded media elements. The sites should just work better.
Gonze Link Love: iTunes Podcasting Letter
Dear Apple,
You did it wrong. Please fix it.
Sincerely,
Lucas Gonze
Oversimplification, but that's basically what Lucas has to say. I will add my link per Lucas' and others request.
iTunes one-click subscription a godawful mess (Gonze.com)