Linked by Thom Holwerda on Mon 2nd Apr 2007 16:50 UTC, submitted by gaukler
Thread beginning with comment 226695
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Good and bad news...
by stew on Mon 2nd Apr 2007 22:24
in reply to "RE[5]: Good and bad news..."
RE[7]: Good and bad news...
by umccullough on Mon 2nd Apr 2007 22:33
in reply to "RE[6]: Good and bad news..."
I guess I'm only stating that despite all the possibilities that might emerge from the open-sourcing of Zeta/BeOS code - it probably won't benefit Haiku much.
If anything, it would likely "destroy" the Haiku project entirely, or probably cause a great number of people to lose interest in it. A great many people will end up flocking to the "official" BeOS/Zeta codebase and start building their own distro out of it.
It sounds like you are one of those people. In other words, you would immediately care less about the design choices and code quality of Haiku, and rather have something now. That is not the goal of Haiku.
Imagine if Windows was open-sourced... would that make ReactOS better?
Edited 2007-04-02 22:35







Member since:
2006-01-01
> Don't buy into the "cruft" myth: code doesn't rust.
> It doesn't rot.
There's plenty of cruft in the BeOS source tree. Plenty of badly commented (or worse, commented in random European language) code. Plenty of stuff that works by smoke and mirrors, and a lot of stuff that was never released (the OpenGL based App Server, for example.) However, there's a lot of stuff that *does* work too. I'm sure we'd all be happy to see Net Server on Haiku to fill the gap until the Kernel netstack was finished. And hell, BONE... well.
(I'm guessing of course, reading into other people's comments, including ex-Be engineers and reading between the lines.)