thinnking. the only problem with linux is that (and BeOS shares somewhat the same problem) it is based on c++ (or c) which is the source of many, many problems with improper programming. writing a program in c++ is one thing, making it stable another but making it really good is a masterpiece.
anyways. i see that i'm producing a war in here because of this simple statement i throw into it. don't be offended. open source has the idea of allowing all to participate. it just does not define in what sense.
i refered in this one more about the driver load and compatibility load. what makes windows a pain in the ass to use and makes linux sometimes a pain to config is the attempt to satisfy a large amount of devices out there. i mean i still cannot use my networking card i especially bought once to work under linux, windows and beos. somehow the driver doesn't recognize the card although the chip should match the drivers.
c++ is the source of evil... procedural programming in this special case. most of those bugs are buffer overflows or underflows which result in a wrong usage of memory. as long as you rely on c++ as your main os language you will always confront those problems. a good framework can reduce the problem but not extinct it.
i'm eager to see your good work though... but i'm more eager to fully compile BeOS from scratch... BFS: BeOS From Scratch ^_^
