RSS feed
<< 24 August 2006 | Home | 26 August 2006 >>

Second dissappointing thing about the Apple Mac

So I'm still waiting for the replacement for the first one that came, and was dead. Should be here next week. But that's not the dissappointing thing (well, not the second dissappointing thing).

Yesterday, I committed some changes to the current development branch. A Macintosh-using developer (quite a few of our developers use Macintoshes as their personal computers, although the company-standard for a developers workstation is a 64 bit, 2GHz AMD desktop with 2Gb RAM, 2 x 17" monitors, and Ubuntu desktop Linux operating system), IM'd me and said 'YOU BASTARD'.

So I was all like, 'Say Again'?

He replies, 'You committed a file called Home and there is already a directory there called home/'

Me: 'Huhhhh? Why does this matter'

Dev: 'The Macintosh uses a case insensitive file system'

SSSSCCCCCRRRRRREEEEEE!!!! SAY WHA???

The Macintosh Uses A Case Insensitive Filesystem?! How can this be? It's a Unix, right? But no, it turns out this wonder of modern computing uses a file naming system straight out of 1979.

Yeah, OK, so you CAN get a case-sensitive filesystem ... by reformatting the disc. When I google about that I get pages returned with titles like 'The Dangers of case-sensitive HFS+'. Dangers? WTF?!

If these dangers can be overcome, reformatting will obviously be the first task I do to it if I ever, ever, receive my mythically on-order and maybe-delivered-next-week after-a-month-of-waiting new 15" Macbook Pro. But srsly? A CASE INSENSITIVE FILESYSTEM IS INSTALLED BY DEFAULT? What barrel-full of retarded monkeys decided on THAT? Its enough to make me wonder.