Once you realize that documentation should be laughed at, peed upon, put on fire, and just ridiculed in general, then, and only then, have you reached the level where you can safely read it and try to use it to actually implement a driver.

Me trying to make a business around Linux would have been a total disaster.

The NIH syndrome (Not Invented Here) is a disease.

I've been employed by the University of Helsinki, and that has been paying my bills. Obviously a ''real job'' pays better than most universities will pay, but I've been very happy with this arrangement I get to do whatever I want, and I have no commercial pressures whatsoever doing this.

You know, the mark of intelligence is realizing when you're making the same mistake over and over and over again, and not hitting your head in the wall five hundred times before you understand that it's not a clever thing to do.

In many cases the user interface to a program is the most important part for a commercial company: whether the programs works correctly or not seems to be secondary.

I don't think commercialization is the answer to anything. It's just one more facet of Linux, and not the deciding one by any means.