OK, so you got this new file system, does all kinda new shit, but you can't come up with a new, oh-so-slick metaphor for it? And that kills the entire project?!? The wingnuts there are more stupid than even I thought.

The answer is too fucking simple. You simply take the new slick underlying file system, and place the old, existing, boring, unexciting, no-sizzle-but-lots-of-steak, everybody-knows-how-to-use-it-except-that-guy's-grandmother file interface, and splice it onto the front end. Then, as time goes on and smarter people than Micros~1 apparently they have start fiddling with it, they can later splice on the new, ohhh-so-k3wl interface onto it (and, since this is Micros~1, kill the old interface that the entire installed base knows how to use).

What the fuck, this is an "object" database, ain't it? And wouldn't you assume that an object database would have an object design? You know, implementing interfaces and all that?

But I guess this is another case of Micros~1 marketing weenies driving the technologists (read: form over substance), where we can't have a new and potentially useful feature without throwing out 60-some years of computing history along with it, now, could we? That wouldn't make sense to the Marketeers, and we know which tail is wagging that dog. So because we can't come up with enough splash to "exploit" this new file system, they'll just kill it ("I'm taking may ball and bat and going home!").

I'm not going to miss Bill Gates in the slightest! Good riddance, you moron.