Author chosen to finish The Wheel of Time – When Robert Jordan died, he left behind his work on A Memory of Light, the final volume of his epic fantasy series, The Wheel of Time. His wife & editor has chosen Brandon Sanderson
Epic Pooh – Michael Moorcock on the state of fantasy literature, originally written in the 1970s but updated for the 21st century. The title comes from comparing the style of Lord of the Rings to Winnie the Pooh. I have no problem reading and enjoying both his work and Tolkien’s, and it doesn’t bother me that Phillip Pullman dislikes Tolkien’s work as well. (Link via something I was reading a few days ago.)
The Happy Endings Foundation [archive.org] – “originally founded in 2000 by Adrienne Small after she read the first book in A Series of Unfortunate Events by Lemony Snicket to her daughter. As well as making her feel thoroughly miserable, Mrs Small noticed her daughter seemed to take a more negative approach to life.” (Yes, it’s satire.)
And on another note:
Hixie’s Natural Log: Evolution in the species “Companies” – Microsoft’s dominance of the industry has killed off or absorbed many smaller companies. Those that have survived are those with strategies resistant to Microsoft’s tactics. The article looks at Mozilla, Google, and Apple. (via Asa Dotzler)
![[Safari icon]](http://www.hyperborea.org/journal/wp-content/uploads/2007/11/safari-48.png "Safari"){kind=small}
In honor of the release* of Safari 3, here’s a little something we found at Trader Joe’s.
The mug is from the short-lived Mozilla Coffee. It seemed appropriate. Now if I can just track down some Opera Coffee, or Explorer Coffee…
*Safari 3 was included in Mac OS X 10.5 Leopard, released 2½ weeks ago. And it’s included in the 10.4.11 update for Tiger, released today. An updated version of Safari was released today for Windows, but it’s still a beta, according to Apple’s website and the license (even though the about box just says it’s Safari 3.0.4—the same version that’s in Leopard). I’d been planning to hold this until all 3 releases were out, but clearly they don’t feel that the Windows version is quite release-quality yet. So, on the premise that two out of three ain’t bad, I’m posting.
One of the problems with the ubiquitous Get Firefox! Get Opera! etc. web buttons is that while they might encourage someone unfamiliar with the product to check it out, they’re kind of pointless to someone who already uses your preferred browser. Sure, there’s a sense of, “Hey, this author uses Opera too!” but that’s about all it can do.
To make these a little more useful, on my Flash site, I use JavaScript to switch the button if someone’s using Firefox, and instead promote the Spread Firefox site. I’ve written up a similar method for Opera, though it’s less clear where to send people.
I recently discovered that Flock has taken another approach to solving this problem. As you may recall, Flock is a browser based on Firefox, focusing on social networking. It integrates with blogging sites, photo-sharing sites, bookmark-sharing sites and so on.
The Flockstars Extension expands on this by converting the button into a mini-profile. You fill in information like an avatar, usernames at Flickr, YouTube, etc., and links to your website(s). It generates button code that acts like an ordinary Flock button, but contains all this extra information.
The extension reads this information. Visitors to your site who are using Flock and the extension will see an icon in the toolbar, which will pop up a short profile and a menu of all the facets of your online presence.
It’s a cool idea, and seems to fit perfectly with Flock’s target audience. But it only solves half the problem. The browser promo badge is still there, still taking up space. The fact that the profile data is in the button code doesn’t make a difference; it might as well be stored in a set of META tags in the page head.
I’ve been thinking about this for a while, but it’s time to refocus the Alternative Browser Alliance. Mozilla’s Asa Dotzler has referred to Firefox and Internet Explorer as the “mainstream browsers” for more than a year now, and it looks like that’s become true.
The web is no longer an IE monopoly. It’s become an IE/Firefox oligopoly. Firefox is no longer an alternative web browser. It’s sold out, its ads are everywhere, and it even allows people to build Firefox-only code.
So, starting today (April 1, 2007), the Alternative Browser Alliance will no longer promote Firefox.
So what will replace it? I thought about Opera, but most of its install base is on cell phones and PDAs, and we all know the mobile web browser is dead, right? Safari? Well, it turns out that WebKit is shutting down.
So the site will be putting its weight behind iCab. It’s as alternative as they come, and it’s guaranteed to remain that way (since it won’t run on Vista).
Update: Yes, it’s an April Fools joke.
The Mozilla Developer Center has just posted some desktop wallpaper promoting open standards, (and the MDC itself) with the theme, “Please don’t hurt the web. Use open standards.”
Apparently the design was a big hit as a poster at SXSW.
For those who haven’t seen it, the MDC is a great developer resource for web developers, describing lots of standards along with Mozilla-specific information.
(via Rhian @ SFX, who notes that the image is available for use under the terms of the Creative Commons Attribution-NonCommercial license. These wallpapers are also covered by the Mozilla Trademark Policy.)
Opera Watch posted an interview with Firefox co-founder Blake Ross yesterday, in which he talks about Firefox, Opera, and the relationship between the two. When asked about the rivalry between fans of the browsers, he says, “I think it’s ridiculous. Millions of people out there rely on us to make the Web better, not have pissing contests.” I couldn’t agree more. In fact, I launched The Alternative Browser Alliance primarily in response to that rivalry.
I found it interesting that when asked to describe Opera in three words, Ross’ response was: “Our best ally.”
When web designers switch from focusing on a single browser (usually Internet Explorer) to developing cross-browser sites (usually adding Firefox, sometimes Opera or Safari, ideally all three), they often find that things don’t work as expected in the “new” browser. This can be for a number of reasons, including:
A big problem is that when you get into the code, a lot of pages aren’t as specific as the authors think they are. When you write code and test it on one browser, you’re not testing that the code is correct, you’re testing that that browser makes the same assumptions you do.
It’s like ordering pizza.
No, really. Let’s say Internet Explorer specializes in Chicago-style pizza, with a thick, chewy crust. And let’s say Firefox specializes in New York-style pizza, with a thin crust. But each can make the other style of pizza on request.
So you call up Internet Explorer and ask for pizza. They deliver you Chicago pizza, and if that’s what you wanted, you figure your order is fine. If you actually wanted New York style, you make sure that next time, you tell them you want that style of pizza.
But let’s say you like Chicago pizza. You get used to calling up IE and just asking for “pizza,” until one day you’re busy, and ask your roommate to order it. He likes to get his pizza from Firefox, so he calls them up, asks for “pizza,” and you get New York style. That’s not what you wanted. Obviously, Firefox pizza is inferior, because they got the order wrong! Well, no, it’s not, and no, they didn’t. They delivered what they were asked for. If you’d told your roommate to ask for Chicago style, Firefox would have been perfectly happy to deliver that style of pizza.
The moral of the story: always be specific with your code. Make sure it’s asking for what you think it’s asking for (validation helps here). And if something doesn’t do what you expect, make sure you didn’t leave that expectation out of your order.
See also: No, Internet Explorer did not handle it properly
(Expanded from a comment I posted at Mozillazine.)
This is good news: Mozilla will be working more closely with various Linux distributors including Red Hat, Novell, Ubuntu, and yes, even Debian, to coordinate Firefox updates, configuration, etc.
There are two main issues: making Mozilla’s Firefox installer work everywhere (it mostly does, but on some systems you need to install some compatibility libraries first), and keeping the distributions’ versions in sync with the official one.
After the Debian IceWeasel debacle, and Fedora deciding to skip Firefox 2 and wait for Firefox 3, it’s good to know that Mozilla has recognized the problem and is working on it. One key piece of information: Red Hat and Novell will both be providing extended support for Firefox 1.5 past its official EOL next April.
Camino, the Gecko-based web browser designed specifically for Mac OS X, has just released version 1.0… and among the release notes it mentions that it’s a universal binary.
As far as I know, this makes it only the third released web browser to work natively on both PowerPC and Intel Macs, after Safari and Shiira. The Opera 9 previews have been universal binaries, and Firefox plans to have them for their next bugfix/stability release (1.5.0.2, probably sometime next month).
