K-Squared Ramblings

Hazards of Keyless Ignition and Office Chairs.

• Today I learned that keyless ignition makes it easy to accidentally leave your car running. Good thing it was only 5 minutes. #
• The fact that it idles silently (no need to run the motor unless it’s charging the battery) was probably a necessary factor too. #
• Amusing: Apple has released Safari 4.0.4. Seems appropriate for a web browser. #
• By Fox “The Cancelator” standards, waiting 4 episodes to cancel Dollhouse Season 2 is generous. #
• WTF? I just tweaked my *other* shoulder doing nothing more exciting than reaching for my mouse. Nowhere near as badly, at least! #
• Right shoulder seems OK. Left shoulder still recovering from whatever the heck I did to it yesterday. The dangers of…office chairs? #

Upgrading the Web: IE8 Released

Microsoft released Internet Explorer 8 yesterday, for Windows XP and Vista. So if you’re still running IE6 it’s once again time to think about upgrading. (Assuming, of course, that you’re not locked in by corporate policy or another piece of software.)

IE6 is now two versions behind the current release.

IE6 is almost 8 years old (it was released in 2001).

IE6 is lacking in many capabilities that all other modern web browsers have, in web technology, in security, and in features you can use.

You can read a review at Wired, a write-up from the IE team, or a summary of technical changes from WaSP.

Of course, Internet Explorer isn’t the only option out there. There’s Firefox, Opera, Chrome and a host of other alternative browsers that are worth checking out.

If you’re still running Windows 2000 or some other old version of Windows that can’t run IE7 or IE8, I’d absolutely recommend Firefox or Opera. Either will be much better than IE6, both will run on Windows 2000, and Opera will even run on Windows Me and Windows 98 (but you really ought to move to something more current than Windows Me.)

The web is still round

G1 Web Browser Compression

WTF? Android’s web browser doesn’t support compression? Shouldn’t it squeeze all the bandwidth it can, especially if you end up on an EDGE network? #

Hmm, it looks like the G1 just turns compression off when on cell networks for proxying. The network itself may do compression (in theory). #

Installing IE8 RC1 — Or Trying

• Installed IE8 RC1. Installer crashed, and I ended up with IE7…even though I’d been running the IE8 beta before. #
• IE8 installer crashes system. New HW checks out. Bad RAM may have screwed something up before I replaced it. Time for System Restore. *grr* #
• Wow, System Restore is taking a lot longer this time. Maybe it’s actually working? (Or maybe safe mode just makes it slower?) #
• I can’t remember how many times I’ve rebooted this computer today. (And no, safe mode didn’t solve it) #
• Finally got IE8 RC1 installed by telling it not to install updates immediately. The Malicious Software Scan was crashing the system. WTF? #
• Now that I’ve FINALLY got IE8 RC1 running, a cursory check of websites I maintain shows no glaring problems. *whew!* #

Alternative Browser Alliance Update

Just a quick note: I finally got around to updating the Alternative Browser Alliance website. Not the full rewrite that I was planning to do two months ago, but at least it’s now current on things like Google Chrome, Firebug, Dragonfly, etc.

I’ve also released that site under the Creative Commons Attribution-Share Alike 3.0 license, which should simplify matters for translations.

Finally, as a compromise between a full blog and little notes on the home page, I added another Twitter account, AltBrowser, where I’ll post not just site updates but random bits of news, comments, tips, etc. related to the topic.  I don’t have time to maintain yet another blog.  And I’m not convinced the net needs one.

I still hope to do that major rewrite, but this should bring it mostly up-to-date.

The New Browser Switch Campaigns

Rather than looking at campaigns for specific browsers, I’m looking at a class of campaigns that are either promoting a group of browsers, or advocating against the current dominant player: Internet Explorer.

Browse Happy — the classic.

• Goal: Move users away from Internet Explorer.
• Target Audience: IE users.
• Promotes: Firefox.  Also Safari, Opera, and… um… Mozilla.  Hmm, someone needs to update that.
• Pitch: IE is dangerous.
• Method: Banners

Alternative Browser Alliance

• Goal: Keep multiple standards-compliant browsers viable.
• Target Audience: All users
• Promotes: Opera, Firefox, Safari.  Also Flock, SeaMonkey, K-Meleon, Camino,etc.
• Pitch: Competition is good for everyone.  See what’s out there.
• Method: Banners

End 6!

• Goal: Move people off of IE6
• Target Audience: IE6 users
• Promotes: Firefox, Opera, Safari, Flock, IE7
• Pitch: IE6 is outdated, buggy, and unsafe.  Use something modern instead.
• Method: Overlay for IE6 visitors

Save the Developers

• Goal: Move people off of IE6
• Target Audience: IE6 users
• Promotes: IE7, Firefox, Safari, Opera
• Pitch: Coding for IE6 is a pain.  Stop putting us through that.
• Method: Animated drop-down at top of page for IE6 visitors

(Yeah, I’m catching up on old draft posts.)

Dillo Web Browser Updated at Last: 2.0 Release

After several years of inactivity and a quiet relaunch earlier this year, the Dillo web browser has finally released Dillo 2.0.

The open-source project started in 1999 with the goal of creating a small, fast, highly efficient graphical web browser that could run well even on low-end hardware and software. It’s a UNIX application, and runs on Linux, BSD, Solaris, etc. Things stagnated when it became clear that GTK1 was going to vanish, and GTK2 would not fit the project goals, and eventually the browser was ported to the Fast Light Toolkit (FLTK).

If you’ve used Dillo before, some of the improvements in this release are multiple character set support (the old versions were Latin-1–only), tabbed browsing, HTTP compression, anti-aliasing, improved rendering and UI, and smaller(!) memory usage.

It does have its limitations, and a few major items stand out as missing when compared to other modern browsers:

• No CSS stylesheet support.
• No scripting.
• No plug-ins.
• Limited SSL support.

That said, it’s useful to keep around on an older system, or for situations where speed is more important than rendering, or to test how a website works without styles, scripts, and plugins.

I started building RPMs of Dillo for my own use back in 2002, and became the official RPM packager for the project the following year. I’ve posted Dillo RPM packages for Fedora 9, RHEL 3, RHEL 4, and RHEL 5. Other distros will have to wait until I get my build system out of storage or figure out how to convince mock to let me build two packages together.

First Impressions of Google Chrome

Now that it’s live, I’ve downloaded the Google Chrome beta on my Windows box at work.  Thoughts so far:

Good:

• Site compatibility seems to be fine so far, with a couple of minor issues (see the “Bad” section).  Mostly I’ve tested it with a couple of forum sites, LiveJournal, Slashdot, and WordPress.
• I like the simple settings box, with “Basics,” “Minor Tweaks,” and “Under the Hood.”
• It does feel fast.
• Showing the URL of links in the lower left-hand corner is a perfect compromise between the spatial advantages of a permanent status bar and the extra room provided by leaving it out.
• I like the task manager for the browser itself.  It’ll be good for developers, but it’ll also be good for users: as the comic points out, if your browser starts chewing up all available resources, you’ll be able to tell what page/plugin/program is at fault instead of just blaming the browser.

Bad:

• Gears support doesn’t seem to work quite right.  WordPress.com doesn’t detect that it’s available.  Local WP installs with Bad Behavior can’t sync completely.  (It doesn’t send an Accept header on the request for one of the TinyMCE files, which causes Bad Bahavior to think it’s a spambot and triggers a 403.)
• Cookie management is too simplistic.  I like to accept all cookies temporarily, but clear everything when I end my browsing session, with exceptions for sites where I want to stay logged in.  This is easy in Firefox, a little trickier in Opera, and doesn’t seem to be an option in Chrome.
• I have seen it pause a couple of times, with as few as 5 tabs. [edit: these seem to be related to Flash content]
• No Incomplete spell-check.
• I keep hitting the forward-slash key to search within a page, since that’s the shortcut I’m used to in Firefox and Opera.

Do No Evil?

Catching up on Slashdot this morning, I found the article on Google Chrome. Check out the number of comments:

New Browser: Google Chrome

Google Chrome seems to be a multi-threaded open-source browser based on WebKit (with some code from Firefox as well), focusing on making a browser that will work well with web applications.

It’s got built-in support for the Gears API (not surprising). And, like Firefox 3, IE8, and Opera 9.5, it’ll do full-history search & auto-suggest in the location bar. Interestingly, they’ve adopted a couple of UI elements from Opera, including thumbnails of your most-visited pages when opening a new tab (like Opera’s Speed Dial, though in this case the list is automatically generated from your browsing behavior), and putting the tabs above the main toolbar — something that Opera has taken a lot of flack for.

According to the blog post, the first preview release should be out for Windows tomorrow, with Linux and Mac following.

Oddly enough, I found out about it through comics blogs (A Distant Soil, specifically), not tech blogs, because Google hired Scott McCloud (Understanding Comics) to explain what makes the browser different in comic-book form.

Improving Browser Reliability

The IEBlog recently posted about their efforts to improve reliability in Internet Explorer 8, particularly the idea of “loosely-coupled IE” (or LCIE). The short explanation is that each tab runs in its own process, so if a web page causes the browser to crash, only that tab crashes — not the whole thing. (It is a bit more complicated, but that’s the principle.) Combine that with session recovery (load with the same set of web pages, if possible with the form data you hadn’t quite finished typing in), and you massively reduce the pain of browser crashes.

I’d like to see something like this picked up by Firefox and Opera as well. They both have crash recovery already, but it still means restoring the entire session. If you have 20 tabs open, it’s great that you don’t have to hunt them down again. But it also means you have to wait for 20 pages to load simultaneously. It would be much nicer to only have to wait for one (or, if I read the IE8 article correctly, three).

Edited to add:

On a related note, I’ve run into an interesting conflict between crash recovery and WordPress’ auto-save feature. If you start a new post, WordPress will automatically save it as a draft. If the browser crashes, it will bring up the new-post page, but restore most of the form data you filled in. So the title, the text of your post, etc will all be there. But WordPress will see it as a new post, and you’ll end up with a duplicate.

This wasn’t a major problem when I encountered it — I had to reset the categories, tags, and post slug after I hit publish (since I hadn’t noticed that they’d been reset to defaults), and I just deleted the older, partial version of the post — but I can imagine if I’d uploaded an image gallery, I would have been rather annoyed, since there’s no way (that I’ve noticed) to move images from one post to another. Reuse them, sure, but not such that the gallery feature would work.

The Race is On

With the Firefox 3 release imminent, Opera Software has just announced a release candidate for Opera 9.5, “arriving very soon.”

Neither browser has announced a definite release date (though Mozilla has stated Firefox 3 will launch in “late June”), but both are in the final stages. Update: Mozilla has announced a release date of June 17.

Update 2: Opera wins with a June 12 release.

• Read about Opera 9.5 RC1
• Read about Firefox 3 RC2

Summer of the Browser

Firefox: The new release candidate Firefox 3 RC2 is out. No date yet on the official launch, but they’re still saying June. Also, developers are starting to talk work that’s gone into what will become Firefox 3.1, such as completing CSS3 selectors support.

Opera: A new Opera 9.5 preview came out today, showcasing the browser’s new look. Also, the Opera Core team takes a look at what you can do if you put hardware acceleration on the whole browser.

Internet Explorer: IE8 beta 2 is scheduled for August. I’m looking forward to seeing what they’ve done, and figure I’ll start updating sites to accommodate changes. I held off changing too much when IE8b1 came out, because some of the differences were obviously bugs (triggering the Caio Hack, for instance; and yes, I reported it).

Flock has been moving ahead with small, rapid releases, adding integration for new services each time. They just added Digg and Pownce in Flock 1.2 a few days ago. Now they’re getting ready to start on Flock 2.0, which will merge in all the new capabilities of Firefox 3. That means it’ll get new rendering capabilities, better memory management, probably EV certs and such.

Web Browser Milestones Passed

Last October I wrote about some milestones in web browser marketshare. Specifically, I was looking forward to IE7 overtaking IE6, and to Firefox overtaking IE6. Well, both of those have finally happened, at least on this site, and a little more besides. Take a look at these stats from May 2008:

Back when I wrote the original post, I had a series of 5 or 6 milestones in mind, but decided to keep it simple and only post the first two. The next one after Firefox passing IE6 was for Firefox 2+ to pass IE6. I should have been checking in more frequently, since it already has.

So what’s next? Well, I expect to see the following in the next year or two:

• Firefox 3 replacing Firefox 2. It’s already got a strong pre-release following. (Fx2 will stick around while there are still Win98 and WinMe users, but they’re already at less than 1% here and falling.)
• Firefox 1 fading into the sunset in favor of newer, more capable releases.
• Netscape disappearing into history. (It’s already below 1% here.)
• IE6 dropping below 25%, 20%, 10% (watching it go to single digits will be satisfying), and finally 1%.
• Safari approaching 10%. It’s holding steady here, but keeps climbing globally.

Things I’d like to see, but am less confident about in the near-term:

• IE6 disappearing from the radar. There are hold-outs, both at the user and the sysadmin level, plus a sizeable minority on Windows 2000. Plus I think Microsoft is committed to supporting IE6 through the lifetime of Windows XP, which means they’ll keep shipping security fixes until 2014. On the other hand, IE 5.0 is technically still supported as part of Windows 2000, but I see very few IE5 visitors these days.
• IE8 replacing IE7, for most of the same reasons it’s taking so long for IE7 to replace IE6.
• Opera breaking out of its steady marketshare and hitting a solid 5%. That would make them much harder to ignore. (10% would be better, since Safari’s still struggling for recognition at 6%.) Of course, to get there they’ll have to pull off a major publicity coup.
• IE dropping below 50%. Could be done, but it’ll be tough. If there’s no majority browser, it’ll be very difficult to justify building a site for one browser only.

Of course, these will probably all happen faster locally than globally, since the audience seems to skew slightly toward the alternatives, but then local stats are the ones that actually matter for a specific site.