No design, eh? I feel that everywhere I go people complain about the modularity and design of the code they work with, and yes, even BeInc isn't immune to all the horror every single software project under the sun faces. I guess we all get a warm fuzzy feeling when looking at our own code, which can explain why we believe that all code not written by ourselves is absolute crap. As we gain experience, we are disgusted with our own code which was brilliant only 6 months ago. That is a basic fact in the industry we're in. I am positive that OpenBeOS code will initially be bad. As we gain experience, we will revisit each module and redo each component (can someone say refactoring and redesigning - thats why there is so much enphasis on prototyping these days, at least when there is no rush to market). Eventually, after years of pruneing and weeding (Pragmatic Programmer) the code may eventually evolve to a thing of beaty. Thats just a fact of life. Heck, it wasn't until W2K that M$ made a decent OS. How long did it take them? Although academic to discuss now, BeOS would have also evolved to a point where its developers considered it to be "less sucky". Lets hope that Palm do something with the code. Even if they decide its garbage, the best we can hope for is that they throw that garbage our way. One persons garbage, another persons gold. This is the age of recycling, you know. Any ex-BeInc engineer got a floppy (or CDR) with code worth distributing to the underground? -----Original Message----- From: openbeos-bounce@xxxxxxxxxxxxx [mailto:openbeos-bounce@xxxxxxxxxxxxx]On Behalf Of Jean-Baptiste Queru Sent: Wednesday, 5 September 2001 5:13 PM To: openbeos@xxxxxxxxxxxxx Subject: [openbeos] Re: Thread on OsNews... > The thread is disussing BeOS / AtheOS kernel, multithreading, pro/cons of > the BeOS design, ... Oh, you mean, there *was* a design? Damn, they could have told me. >Jean-Baptiste Queru ((ex?) Be engineer) Yes, ex-Be engineer, and probably ex-Be engineer forever. -- Jean-Baptiste Queru <jb@xxxxxxxxx>