The Tiger Details List

Friday, 29 April 2005

So let’s try something a little different.

I’ve been using the final developer build of Mac OS X 10.4 for the past few weeks, and I’m compiling a list of observations and interesting details. Things that are new, things that are different.

I’m going to assemble them together on a single page, but I’m not writing them all at once. Rather, I’m going to update the list continuously over the next week or so. Here’s URL of the article:

http://daringfireball.net/misc/2005/04/tiger_details

You’re welcome to reload that page every few hours, but the best way to follow along will be via RSS; I’ve created a special, temporary RSS feed that will contain just the entries to this list of Tiger details:

http://daringfireball.net/feeds/tigerdetails.rss

In other words, it’s sort of like a temporary mini-weblog dedicated to details about Tiger.

I’m also accepting submissions from readers. What we’re looking for here are interesting details that aren’t obvious and which Apple hasn’t touted. If it’s something Steve Jobs demoed during his Macworld keynote, it’s not what we’re looking for. Submissions don’t have to be original — send links to other weblogs if you see something interesting there first, giving credit where credit is due. And let’s assume everyone has already read John Siracusa’s Tiger review at Ars Technica.

Send your submissions here:

tigerdetails@daringfireball.net

A few notes on submissions:

  • Note that unlike my usual email policy, email sent to this address will be considered attributable. In other words, if I use your tip, I’m going to give you credit. If you don’t want to be named, you must state so explicitly in the body of your message.

  • If you have a weblog or other web site to which you’d like your name linked, include the URL.

  • If you send something and I don’t use it, please don’t take it personally. I’m trying to list only the most interesting details, but what I find interesting is obviously highly subjective.

  • Notes that are well-written are more likely to be used than those which aren’t.

  • Include screenshots when appropriate. PNG is preferred.