SafariWow. I have to admit I was not expecting this at all, but Apple has just announced they’re releasing the Safari web browser for Windows.

Increased consumer choice, of course, is a good thing. The most immediate benefit, though, is that Windows-based web developers (the majority) who haven’t been willing to buy a Mac to test their sites in Safari will be able to do full testing on all four major rendering engines: Trident (IE), Gecko (Mozilla/Firefox/etc.), Webkit (Safari) and Presto (Opera).

Also, there’s some really cool stuff available in recent versions of WebKit that will be great to have available for a wider audience.

Interesting thought: this may be the first browser released since Opera expanded to Linux in ~2000 that is available in the same version on Windows and Mac, but not Linux. Even when Internet Explorer was available for the Mac, it used a different engine than the Windows version did.

I wonder what impact this will have on the development of Swift. Its main claim to fame was porting WebKit to Windows, and it’s been months since their last release.

I also wonder what the status is on re-merging the KHTML and WebKit forks. It’s gotten to the point that Konquerer is only an approximation of Safari, making testing on Linux a little harder than it used to be.

(via Asa Dotzler)

No doubt there’s a 500-comment Slashdot discussion already.

Update: Slashdot’s all over it, and Opera Watch has a thread going as well.

Update 2: I’ve posted my thoughts on the implications for Opera. There’s an update at CSS3.info, where they have previews of upcoming CSS features available in Safari 3.

Update 3: I’ve updated the Alternative Browser Alliance to reflect Safari’s new status. This also solves a nagging doubt I’ve had as to whether the default browser on Mac OS should really be considered “alternative.” On Windows, it definitely is.

Update 4: The Webkit team and Web Standards Project have weighed in. The Windows version of WebKit should be available later today, which will be nice for following progress on issues as it moves from beta toward final version. It turns out there’s a regression and at least the Windows version no longer renders the Acid2 test correctly.

Update 5: The author of Swift says that Swift isn’t going away [edit: the blog has since vanished], and points out that “Swift renders more like a Windows Application, both in the GUI and in WebKit. Safari, looks just like OS X, similar to iTunes 6 and below.” Ever since Apple started porting apps to Windows, I’ve found something odd: A common complaint about third-party Mac software is that it doesn’t look and feel native (one of the big reasons we have Camino as well as Firefox), yet when Apple ports their own apps to Windows, it makes them look exactly the same as they do on Mac OS instead of making them work like native apps. I mentioned this to Katie yesterday and she suggested it might be a case of turnabout being fair play.

After a couple of weeks on Opera 9.20, I’ve come to the following conclusions about Speed Dial:

  1. I can’t stand the portal-like page that loads when I open a new tab. It’s slower than a blank page, it’s slower than opening my bare-bones home page, and it makes it tricky to open a new page and middle-click on an empty area to paste in a URL from another app because it’s too easy to click on one of the thumbnails and open one of the speed dial pages instead. (It’s a Unix thing — middle-click usually pastes the current selection, and if you paste to a web page area, most browsers will try to load it as a URL.)
  2. I love being able to hit Ctrl+1, etc. to quickly load those pages.

Once upon a time, wasn’t there an option to choose what would load in a new tab/page?

*This post originally appeared on Confessions of a Web Developer, my blog at the My Opera community.

Flock. 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.

Opera BrowserThe Opera Web Browser is in the news today. First, they’ve just released version 9.20. In addition to the usual security, stability, and compatibility fixes, they’re promoting a new feature called Speed Dial, to make it easier to reach your most-frequently-visited websites.

Meanwhile, a recent survey by NetApplications and Surveyware found that while Firefox is widely considered the best browser, Opera’s users are more satisfied than users of any other browser. NetApplications’ current marketshare shows 79% IE, 15% Firefox, 4.5% Safari and 0.8% Opera for March 2007. (via OperaWatch)

While Opera is an excellent browser, this high level of satisfaction may be in part because of the size of its userbase. Often, when something is only followed by a small fraction of the potential audience, it’s mainly the hard-core fans. The only way to grow past that size is to bring in the casual users, who are less invested in it. Only time (and increased marketshare) will tell.

Webuser decided to lead with the Opera findings, which is great news for what they call “one of the internet’s best-kept secrets.” But they made an odd choice on the image to run with the article:

Screenshot of WebUser Article: Opera headline, Firefox Logo

Maybe they figured the Firefox logo was more recognizable, and would get more people to stop and read?

Alternative Browser Alliance - New LogoI’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.