Linked by Eugenia Loli on Wed 15th Oct 2003 22:47 UTC
Mac OS X I was able to try out and preview Mac OS X Panther 10.3 for the past few months after WWDC and for the last few days I am running a latest version. So, what to expect from Mac OS X when it comes out on the evening of October 24th? Come in and have a look in this preview article. Update: screenshots removed at request of Apple.
Permalink for comment
To read all comments associated with this story, please click here.
From everything I heard...
by Bascule on Thu 16th Oct 2003 08:14 UTC

I have serious doubts as to whether the new Finder was written from "scratch". To begin with, by all reports the new Finder is still a Carbon application. I see absolutely no reason why Apple would have used Carbon over Cocoa for something like the OS X finder, considering portability back to OS 9 would certainly not be an issue. Second, it sounds as if kqueues are not being fully utilized for filesystem event notification (although they probably are for the search feature)

Not that this is necessarily a bad thing. For those of you who read Joel on Software he has written some excellent articles on refactoring versus rewriting:

Here's a pertinent portion of the first article:

"Before Borland's new spreadsheet for Windows shipped, Philippe Kahn, the colorful founder of Borland, was quoted a lot in the press bragging about how Quattro Pro would be much better than Microsoft Excel, because it was written from scratch. All new source code! As if source code rusted.

The idea that new code is better than old is patently absurd. Old code has been used. It has been tested. Lots of bugs have been found, and they've been fixed. There's nothing wrong with it. It doesn't acquire bugs just by sitting around on your hard drive. Au contraire, baby! Is software supposed to be like an old Dodge Dart, that rusts just sitting in the garage? Is software like a teddy bear that's kind of gross if it's not made out of all new material?"

Personally, I'd prefer it if Apple recycled large portions of the old Finder for the new one... it will make for a better overall Finder as much of the code will have already undergone extensive debugging and testing. Apple certainly hasn't been one to throw the baby out with the bathwater and scrap perfectly good programs when they're simply in need of a few modifications here and there.

I'd certainly find reusing portions of the old Finder preferable to discovering that Apple did in fact rewrite Finder from scratch, using Carbon for the API and reimplementing a bunch of polling code to monitor changes in the underlying filesystem, rather than using kqueues for proper filesystem monitoring.

(Unfortunately, I think this still means no Cocoa Gestures support for the Finder... would've been nice)