Why the driver issue isn’t

Filed under: Uncategorized — 2005-08-18 @ 10:39:15

I was reading the apple matters post by Chris Seibold and he's right. 99% right. Apple computers are uncle ben's rice.

Rice, much like the bulk of computers sold today, is a commodity product. When something is a commodity it more or less means that all versions perform to the satisfaction of most users. To use rice as an example Uncle Ben’s Instant Brown rice performs exactly as generic instant rice. Both varieties are limited governmentally by the number of rat hairs and insect parts present and both cook up precisely the same. Yet a lot of people buy Uncle Ben’s rice. If, as I did, you ask yourself why you’ll realize that in a commodity based market there is room for a few brands to actually be desirable for reasons unrelated to function. Whether the brand is hip, or provides prestige to the buyer there are loads of people willing to buy something that reflects their lifestyle or taste.

But Chris is off in one big respect. The driver issue. This is something that has been toted up-and-down, back and forth by probably every single mac blog on the internet.
The crux of the driver issue is the idea that mac os x only runs on a limited subset of hardware by design and that it will probably be impossible to run it on hardware that it wasn't intended to run on. This is false. Mac OSX is at it's core an open source operating system and people have been able to for a long time roll your
own OSX kernel. I personally have done some of this, I used that last link, under kernel, to patch my mac and enable me to spoof mac addresses. Why I wanted to do this is a story for another day but I digress.
The kernel, for all of those who are not familar with it is the core or the, umm, kernel of the operating system. The kernel is what makes it all tick. That means that the kernel, the core of the OS contains things such as network, video, sound drivers. This means that if your network card isn't supported, you can port the driver from FreeBSD or just write your own. The same thing with any of the other components of the core system. It doesn't work on your hardware, hack it so that it does. This seems exactly like what the OSX86Project should be doing.

No Comments »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a comment

Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>

(required)

(required)