Linked by Thom Holwerda on Fri 23rd Oct 2009 21:13 UTC, submitted by poundsmack
Mac OS X John Siracusa, the Mac OS X guru who writes those insanely detailed and well-written Mac OS X reviews for Ars Technica, once told a story about the evolution of the HFS+ file system in Mac OS X - he said it was a struggle between the Mac guys who wanted the features found in BeOS' BFS, and the NEXT guys who didn't really like these features. In the end, the Mac guys won, and over the course of six years, Mac OS X reached feature parity - and a little more - with the BeOS (at the FS level).
Thread beginning with comment 390731
To read all comments associated with this story, please click here.
I really wish they wouldn't
by Bill Shooter of Bul on Fri 23rd Oct 2009 21:35 UTC
Bill Shooter of Bul
Member since:
2006-07-14

I just fear, absolutely fear Apple homegrown protocols, file systems, standards, ect. Too much marketing smoke and reality distortion accompanies them, with too few details. The most useful homegrown thing they've ever, ever done is firewire.

Reply Score: 6

RE: I really wish they wouldn't
by Burana on Sat 24th Oct 2009 07:53 in reply to "I really wish they wouldn't"
Burana Member since:
2009-01-26

I just fear, absolutely fear Apple homegrown protocols, file systems, standards, ect. Too much marketing smoke and reality distortion accompanies them, with too few details. The most useful homegrown thing they've ever, ever done is firewire.


Absolutly. Until they get something serious, they will hack something together, put a "bling-bling" interface on it, and call it "innovation".

And boy, will they patent it!

Reply Parent Score: 1

RE: I really wish they wouldn't
by Tuishimi on Sat 24th Oct 2009 16:18 in reply to "I really wish they wouldn't"
Tuishimi Member since:
2005-07-06

Do they usually work?

Reply Parent Score: 2

subterrific Member since:
2005-07-10

While not entirely homegrown inside Apple, I think Zeroconf is a good example, possibly the only example, of a good protocol to come out of Apple.

Link-local addressing
Multicast DNS
DNS Service Discovery

All good standards. Though we have yet to see Stuart Cheshire's vision of Ethernet and/or TCP becoming the standard protocol for all devices (TCP keyboard and mouse anyone?), I think Zeroconf is still a huge success.

The bad example I come up with is resource forks. While adding structured data storage to files isn't a bad idea, the way it was implemented at the file system level made it very difficult to exchange files with non-HFS systems. This might have been what the UNIX guys at NeXT didn't like about BeFS, it had the ability to store extended metadata attributes attached to a file that would be lost in a copy to another file system. If I remember correctly, the address book in an early version of BeOS was implemented using file attributes, which was cool in your walled off BeOS corner of the universe, but if you copied a "Person" file from BeFS to another file system or even tried to send one to another BeFS system using a protocol that didn't support copying file attributes you'd end up with a useless 0 byte file. However, BeFS did support HFS resource forks by storing the raw fork data as a file attribute.

Reply Parent Score: 2

jgagnon Member since:
2008-06-24

I've often wondered why Ethernet couldn't be more pervasive as an interconnect of devices. It would simplify so many things from an IT standpoint and it is plenty fast enough for the majority of devices, especially since you can run 10/100/1000 on the same lines (not sure about 10GB). Heck, 10 GB Ethernet is faster than many (most?) hard drives can keep up with.

Reply Parent Score: 1