Fedora Linux.I haven’t been following the progress of Fedora 9 very closely (possibly because it took me until last month to finally upgrade my home PC to Fedora 8), but as the release date of April 29 May 13 approaches, I thought I’d take a look at the release notes for an overview of what’s new. Of course there’s the usual upgrades to the various desktop environments, including, finally, KDE4, but something that surprised me was the inclusion of Firefox 3 beta 5.

Admittedly, Linux distributions often include non-final software by necessity. Many open-source projects spend years in the 0.x state not because they don’t work well, but because the authors don’t feel that it’s complete yet. (Often, a project will take their checklist and build feature 1, stabilize it, add feature 2, stabilize that, etc. so that you get a program that’s a stable subset of the target. Off the top of my head, FreeRADIUS was quite stable long before it hit 1.0, and Clam AntiVirus has been quite usable despite the fact that its latest version is 0.93.)

FirefoxLately, though, there’s been a tendency toward sticking with the latest stable release, at least for projects that have reached that magical 1.0 number. Sometimes they go even further. Only a year and a half ago, Fedora planned to skip Firefox 2 and wait for version 3. (Clearly, they expected Firefox 3 would be out sooner!) So it was a surprise to see that this time, Fedora has decided to jump on the new version before it’s finished.

When the first Firefox 2 beta was released, I looked into Microsummaries, a feature that enables bookmarks to automatically update their titles with information. I concluded they were useful, but not for anything I was doing. The main application would be my Flash site, but it already had an RSS feed for updates, and a microsummary could only really include the most recent item.

Now the first IE8 beta supports Webslices. They’re similar in concept, but can include formatted data (not just plain text) and use microformat-like markup on the web page instead of a <link> element in the head.

I figured with two browsers supporting the concept, I’d give it a shot. I adapted the script I use to generate the RSS feed so that it will also take everything on the most recent day and generate a text file, which is used for the Microsummary title. For the Webslice, to start with I just marked up the “Latest Updates” section of the home page. Since I haven’t installed IE8b1 at home, I’m using Daniel Glazman’s experimental Webchunks extension for Firefox to try it out. Unfortunately the extension doesn’t seem to resolve relative links in its current state.

The real question, of course, is whether either technology offers anything better than what feeds can do now.

I think I’ll end up going the external-feed route for the Webslice as well, since it’ll use a lot less bandwidth than having a bunch of IE installations pulling the entire home page once a day. Plus since I’m using SSI on that page, it doesn’t take advantage of conditional requests and caching, and a static file will. But that’ll have to wait. Lost is on in 2 minutes, and after getting up earlier than usual this morning, I’ll probably be going to bed right after the show.

Update: I checked in IE8, and the webslice does work as expected. A few minor differences: Webchunks pulls in external styles, like the background and colors, while IE8b1 only uses styles in the chunk itself. Interesting bit: I’m marking up list items as entries, and IE8 is actually displaying them as a bulleted list, while Webchunks is simply showing the content.

So it at least works. Maybe tonight or Sunday I’ll see if I can refine it a bit.

FirefoxOne of the biggest complaints about Firefox since 1.5 was released has been its high memory usage. Go to a forum anywhere and you’ll get people griping about “have they fixed the leak yet?”

It is, of course, much more complicated than that. There are caches, fragmentation, places where memory is used inefficiently, bunches of small leaks, leaks that only happen under specific circumstances, leaks in extensions, leaks triggered by combination of extensions, etc.—not one single leak that can be fixed. And then there was the unfortunate post in which one Mozilla developer (I’m too lazy to look up who) pointed out that 1.5 stored more information in memory, and that probably had a bigger impact on total memory size than actual leaks, which many people on the Internet jumped on as “It’s not a bug, it’s a feature.” (Why should they bother to read what was actually stated, when they can just read a misleading but sensational summary?)

A lot of the small leaks were patched in bugfix releases for 1.5 and 2.0, but really big changes are coming in Firefox 3. Mozilla’s Pavlov has written a detailed post on Firefox 3 Memory Usage, describing the different categories of memory improvements that have been made in the Firefox 3 development cycle.

I wouldn’t be surprised to find that this is one of the big reasons Firefox 3 has taken so much longer than previous releases. I suspect it’s time well spent, though, and users will be happier with a later, lighter Firefox than with one that shipped earlier, but used just as much memory.

(via Asa Dotzler)

Opera.Firefox.I’ve been using the Opera 9.5 previews across the board since September, and the Firefox 3 beta 2 on my secondary work computer for the past month, and I just can’t bring myself to go back. The full-history search available in both browsers has got to be the most useful new feature I’ve seen in a browser since inline spell-check.

Really, the only things holding me back from jumping up to Firefox 3 on my main computers at home and at work were Firebug and some of the HTML validator extensions. Firebug is complicated enough that I didn’t want to rely on the Nightly Tester Tools to disable the compatibility checks. Then I found out that there’s a Firebug beta that does work with Firefox 3. That was enough. Last night I took the plunge.

IE7Meanwhile, things look good on the ditch-IE6 front. After last month’s false alarm due to a local maximum, it looks like IE7 has solidly overtaken IE6 on this site! For the first 13½ days of January, Internet Explorer accounted for 62.5% of total hits. IE7 was 33.5%, and IE6 was only 28.4%. Even better, that’s barely over 1 percentage point from Firefox’s 27.2%!

Most likely, a lot of people got new computers for Christmas. New Windows boxes would mostly be Vista, and would ship with IE7. Another factor might be techies visiting their relatives and helping clean up/update their computers. They might have taken the opportunity to install IE7 or Firefox.

VXWorld: Crossing the Uncanny Valley – on the current state of the art of photorealistic computer animation, from Final Fantasy through Polar Express to Pirates of the Caribbean and Beowulf. As pointed out, one reason that Davy Jones worked so well is that he doesn’t look human. (via Neil Gaiman)

Firefox Floppy Disks – remember when software came on 3½-inch floppy disks? Or 5¼″? Just for fun, someone split the Firefox installer across 5 disks, complete with appropriate labels… and even took it a step farther