Canonical discloses the behaviour, no reason for paranoia.

Check out this article (http://www.slate.com/blogs/blogs/thewrongstuff/archive/2010/08/03/error-message-google-research-director-peter-norvig-on-being-wrong.aspx) on Google's timing and method for new projects, it sheds some light on what goes on in there.

FreeBSD gets by democratically enough...

I mentioned these because in all of them the manuals add to the gaming experience - SC2K's manual has amazing artwork, Homeworld's throws you into a complex historical complex and Infocom text adventures had "feelies" (http://en.wikipedia.org/wiki/Feelie). It's not about teaching you the keys and so on - it's about purpose, about making the game more than a button-mashing, mouse-clicking race filled with pretty tesselated graphics. I still play SC2k, Homeworld (1, Cataclysm and 2) and the occasional Z-Machine story file.

Not good, at least for me. And if you take a look at the manual for Sim City 2000 or Homeworld or any Infocom text adventure, you'd realize manuals can be an integral part of the gaming experience. But hey, all players want these days are FPS', so why bother right? :|

Yeah... or a local mirror of Wikipedia. I get it!

Dude, do you really think so? I get the whole handheld Crysis thing, but 1TB of data on a personal database? What for? (hey, don't quote me on this, ok?) :D

The end to "can it run Crysis?" jokes!

Someone's open WiFi connection? Really? :D

Dump'em here or it doesn't hold :D

In this economy, they're gonna need it...

You're wrong, sir.

In fact, being Java based can be helpful to an OS:

Because Java is a type-safe language, JX is able to provide isolation between running applications without needing to use hardware memory protection. This technique, known as language-based protection means that system calls and inter-process communication in JX does not cause an address space switch, an operation which is slow on most computers.

This is from JX's page on Wikipedia. I know it *sounds* terrible, but first try to use an OS written in Java - then you can tell the world how slow it is.

KDE != Linux -> granted! How long do you think it will take to port it to Haiku? :D I hope Haiku succeeds as well, but there's a number of things here that may contribute to its implosion: 1 - it's not multi-user (yet) and I don't think it's the kind of thing that can be an after-thought - maybe in this case it can be, since it's contemplated for in the design, just not realized 2 - no WiFi - seriously? should be a top priority IMHO 3 - GCC2 - it's there for compatibility with BeOS, but who needs it still? 4 - kernel code in the hands of "relative newbies" - they're not kernel pros, so catastrophic crashes are a possibility, which makes me cringe (like blowing up on USB pendrive insertion and such) 5 - it's not attracting devs - why? it's such a cool platform! but I guess BSD/Linux already take up all the free talent in the world :| 6 - only C++ - we need Mono, Lua, Ruby,etc, etc, - with Haiku API bindings 7 - limited hardware support - I know, it can only get better, but with few devs it will take long I'm not bashing Haiku - I just think the alpha should have been out the door long, long ago. Even Linus had to push 2.6.0 before it was ready so people would pay attention to it...

Haiku != Linux. Amarok is very deeply connected to KDE/Qt APIs which are, of course, not implemented in Haiku. Although ports can be considered (Firefox is a must), maybe a player designed for Haiku's APIs would be best for Haiku at this stage, even as a showcase.