Catching up, part two

This time, the focus is on Macintosh goodies. All you PC-using heathens can read on in wistful fantasyland, or just find something else to do — like reinstall Windows again. ;)

  • Enough people linked to PerversionTracker that I finally had to take a look. Looks like I’ve got another regular read! Any site that the Opera webbrowser has “taken the cake, and it is filled with plague and cottage cheese,” and that it is “slower than a squashed waterbear” defintely gets my approval. (Via Brent Simmons, along with many other Mac-based weblogs)

  • I’m probably the last Mac afficionado to find out about this, but it looks like Safari is actually going to get tabs. Nifty! (Via MacSlash, MacRumors and others)

  • This could be a fun toy to play with: VoiceBox, a tiny app that will take text files and convert them to audio files using the Mac’s speech synthesis. It will even ‘read’ RSS feeds, so I could listen to websites on my iPod while going to work! Useful? Dunno yet. Cool, though. (Via Rael Dornfest)

Apple bloggers?

There’s been much discussion recently regarding Microsoft bloggers, i.e., people who work at Microsoft and blog. I read a few of them (both because they’re good blogs, and because of the whole “know your enemy” philosophy [grin]).

Got me thinking, though — what about ‘Apple bloggers’? The only one I know of off the top of my head is Dave Hyatt, who works on the rendering engine for Safari. Any others out there I should know about?

Surfin' Safari

Dave Hyatt has got to be one of the bravest people on the ‘net I’ve seen. Consider…

  1. He’s a developer for Apple, working on their Safari web browser…
  2. He keeps a weblog where he…
    1. Tracks and responds to what people are saying about Safari, good and bad…
    2. Reports on which bugs have been fixed and which are being worked on
  3. …and on top of all that, he’s actually soliciting requests from readers as for what they’d like to see in Safari!

Kudos to Dave for being crazy enough to do this, and to Apple for allowing him to do this. More companies need to realize that this is a real, effective way to encourage their users. We know that Safari is being worked on, we know that it’s being worked on by someone who genuinely cares about the project, and we know that they care about and listen to what their customers want to see in the product. I can’t think of a better way to build and keep customer loyalty than that.

R.I.P. Opera

While there had been rumors of an Apple-branded web browser for a while, Safari‘s introduction at this most recent MacWorld took a lot of people by surprise, and watching the reaction has been quite interesting. Yesterday, Opera Software (makers of the Opera webbrowser) announced that they may stop development on the Mac version of their browser.

I’d say bummer — except that every time I tried Opera on my Mac, I was severely unimpressed.

The C|Net article, however, made me raise my eyebrows quite a few times as I read it over.

Specifically, [Opera CEO] Tetzchner said that he had asked Apple whether it would be willing to license Opera either to replace KHTML, or to supplement the current Safari version, which Apple said is a stripped-down affair with a minimalist interface and limited feature set.

“We have contacted Apple and asked them if they want a third-party browser, and we’ll see what the answer is,” Tetzchner said. “They could say we want to use Opera as the core engine. If they want KHTML as a simple little browser, and also something more advanced, we would be happy to provide it. Obviously, if we don’t get any positive signs from Apple, then we have to think about it.”

You’re kidding, right? After Apple has taken the time to create Safari, which has been getting good reviews all across the web, does Opera really think that they’ll suddenly decide to reverse direction, tear Safari down and rebuild it with an entirely different rendering engine? One that isn’t open source, and isn’t nearly as solid as the KHTML engine that Safari is currently using? I just don’t see that happening. And, apparently Apple doesn’t either:

“We think Safari is one of the best and most innovative browsers in the world, and it seems our customers do too,” the Mac maker said in a statement. “No one is making Mac users choose Safari over Opera — they’re doing it of their own free will — and Opera’s trashing of Safari sounds like sour grapes to us.”

Later in the article, C|Net gives us this:

Last quarter the online music service MusicMatch decided to drop its service for the Mac, following Apple’s release of the competing iTunes application.

At the time, MusicMatch reasoned that with Apple directly competing with it for an already small pool of users, maintaining development on a Mac version no longer made business sense.

Now, the PC version of the iPod uses a custom version of MusicMatch Jukebox on the PC for all the features that iTunes provides on the Mac! Sounds to me like even if MusicMatch did decide to drop their native Mac support, they didn’t exactly end up entirely on the losing end of the deal. While quite possibly a technically correct few sentences in the article, C|Net sure makes it sound like Apple did MusicMatch far worse than is actually the case. Anyway…

“It’s not a platform where we’ve earned a lot of money,” said Tetzchner. “It’s a business decision. We have been putting a lot of resources into the Apple version and think we have a much better product, but it’s still a question whether it’s worth it.”

Well, y’know, if you’d made a better browser, maybe you would have fared better. The times I tried Opera, it was slow, kludgy, had some very odd rendering issues, and had a huge, obnoxious ad banner embedded into the free version. When there are other free browsers available, even pre-Safari, that were smaller, faster, more accurate, and less intrusive, why would I choose Opera? Sour grapes, indeed.

(Via Safari developer Dave Hyatt)

I need a drool cup

Oh my lord.

Apple just revamped their desktop line and dropped prices — severely — on their monitors.

Their Power Mac G4 line is now available in single-1Ghz, dual-1.25Ghz, or dual-1.42Ghz models, and the mid-range dual-1.25Ghz model starts at \$1999.

Prices on their LCD monitors have dropped precipitously. The 17\” model dropped \$300, from \$999 to \$699, they introduced a new 20\” model at \$1299, and their top-of-the-line 23\” model dropped \$1500, from \$3499 to \$1999!

I really need to get my money saved up….

Jobs for everyone

I doubt this is very serious (or likely), but apparently someone has set up a grassroots movement to elect Apple CEO Steve Jobs president!

The site, unfortunately, is currently slashdotted, but there’s some great comments in the /. thread

well, the mac community is probably larger than the perot community. ;)

rojo\^

“I hereby declare that The White House will no longer be boring”beige”, it shall be painted”Lickable Blueberry\”.

The Apple hoardes debate among themselves whether the country is now just “insanely” better, or “miraculously” better.

Reality Master 101

The White House will remain white, but all the plaster will be replaced with translucent white plastic.

The capitol dome will be redone in anodized aluminum. It will also have firewire.

protein folder

[This is illegal…] Due to the seperation of church and state.

Steve cannot be both God and President without violating some part of the constitution.

Of course, given recent events, that ‘problem’ can probably be remiedied.

asparagus

Browser Daydreaming

A few days back, Phil asked what we’d like to see in a web browser. I initially responded in my usual semi-flippant fashion, but after running it through my head for a couple days, I’ve actually got some ideas.

To start with, I’ll look at web browsers as divided into two core components, as outlined by John Gruber on Daring Fireball:

It is essential to understand that there are two huge, almost completely separate tasks involved in producing a web browser. The first is the HTML rendering engine — the part of the browser that parses HTML and turns it into an on-screen graphical representation. The second is the browser application: the windows, menus, buttons, and dialog boxes.

I’ll start with the second part — the application itself. The things I’m most interested here are scattered across multiple browsers at the moment, and I do end up wishing that they were all in one package. Key things I’d like to have in my ‘ultimate browser’:

  • Safari’s clean, simple interface (without the ‘brushed metal’ look, though).
  • Safari’s speed.
  • Chimera’s tabbed browsing (unless someone can come up with something better).
  • Safari’s bookmark management.
  • Internet Explorer’s form autofill.
  • OmniWeb’s beauty.
  • The ability to tab among all page elements — links, form elements (text fields, buttons, and menus).
  • Full-featured contextual menus (Safari’s are pretty anemic at the moment).
  • And there’s probably more that I’m not coming up with at the moment.

When looking at the other side of the browser experience, I was kind of inspired by Jason Kottke’s browser integration musings and Mark Pilgrim’s wondering if Safari should be intentionally buggy (and for the record, no, I don’t believe it should, but that’s another post for another time).

Dreaming about the perfect UI for a browser is all well and good, but we’re still faced with the dilemma of which rendering engine to use. Each of the major engines out there (IE Mac, IE PC, kHTML [Safari, Konqueror], Gecko [Chimera, Mozilla, Netscape], Opera and OmniWeb] has its own collection of bugs to be worked around, causing frustration for both web designers trying to design sites that look equivalent under all browsers, and for end users who, depending on their level of expertise, may or may not understand why any given site doesn’t seem to work in whatever browser they use.

So, what I’d kind of like to see, would be a plug-in based interface for the rendering engine, easily changed via a menu choice somewhere. Find a way to wrap the latest build of any given rendering engine in a small piece of plug-in code, and drop it in an “engines” folder for the browser app. The app would come with one default engine (and as long as I’m living in a perfect fantasy world, let’s make that engine an as-yet mythical completely strict standards-based engine), but at any given point, you could go to a menu and switch to another rendering engine, which would then re-render the current page (or all pages — let’s add a preference option to select whether rendering engines would apply on a global basis or window-by-window) with whatever engine was chosen, which might be less strictly accurate, but might be more compatible with whatever mess of code the user is currently attempting to view.

I have no idea how feasible something like this might be, and I don’t think it’ll ever happen, but hey, I like the idea. Of course, in a perfect world, I’d much rather see standards-compliant websites that worked in standards-compliant, bug-free browsers, but I don’t expect that’ll be happening anytime soon. I can dream, though….

More on Safari

In order to give it something of a workout, I went ahead and set Safari to be my default web browser. I’ll probably keep it here for the next couple days to stress test it, then switch back to Chimera until Safari moves out of beta status.

Mark Pilgrim has a good rundown of current CSS bugs that he’s uncovered in Safari so far (thankfully, though, it renders djwudi.com just fine). Amusingly enough, I may have just found one more while I was reading his post: while most of his links highlight correctly when the pointer is over them, the ‘First test case’ link towards the end of the post that has \<code> tags within the link displays oddly — the code snippets disappear! Here’s a couple quick screenshots of how it looks in Chimera and in Safari:

Chimera renders the link correctly...

...while Safari blanks out the code snippets!

I’m also finding that I (along with many other people) really miss the tabbed browsing available in Chimera and Mozilla — once you’ve gotten used to it, it’s really hard to go back to having window after window all over the place. Still, the speed is definitely good, and overall, it’s not too shabby. Just definitely a beta release. Here’s hoping that future releases are as impressive as the first shot!

Thoughts on the keynote

Just a couple quick thoughts I had regarding some of the news from Steve Jobs’ keynote speech today at MacWorld.

  1. Apple plays nice

    Apple is continuing to support the Open Source software movement. Not only have they been utilizing the Open Source community to help improve the code for OS X, but they’ve done the same with Safari, the newly announed browser. On top of that, after dramatically improving the code base that Safari uses, they are sending the improved code back into the community for public use. Very nice move.

  2. Apple plays nice, part 2

    I noticed a nice little feature in Safari during the few moments I was able to play with it before I left for work. In the main Safari menu, just underneath the ‘Preferences…’ option, is an option to disable popup windows. While the option has been around in most Mozilla-based browsers for a while (sometimes easily available, sometimes not), it’s nice to see Apple including the functionality right off the bat in their browser.

  3. Open format files

    The announcement that Keynote (the new presentation application) uses XML for it’s saved project files really got my interest. While I haven’t played enough with XML to be able to take advantage of this right off, I can think of some very interesting scenarios that could make this very useful.

    Say, for instance, a script that weekly (or monthly, or daily, or whatever) pulls the Apache logfiles from your OS X webserver, extracts whatever key data points you want to extract from them, and plugs the resulting data into the right spots inside the XML file of a predefined Keynote template. Bingo – an automatically generated weekly professional presentation of your website’s traffic, most visited pages, most frequently used search terms, etc., ready for presentation to your boss, board of directors, whatever. Or, since Keynote can export to PowerPoint, you could have the report ready to send off to those Windows-based heathen. Or just export the report to a PDF file or QuickTime movie for posting on a website. All automatically generated, without the need for any interaction beyond the initial setup.

    Pretty damn cool, I think.

In the meantime, I’ll just go drool over that 17\” Powerbook now…