Linked by Andrew Hudson on Tue 23rd Feb 2010 00:23 UTC
Permalink for comment 410466
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
More News »
Sponsored Links



Member since:
2005-07-24
BeOS supported 'n' CPUs, Haiku had the same aim.
Even BeOS can take advantage of however many CPU cores are available, provided it can support the chipset / memory.
From what I hear wireless works very well, but is not tested well enough to consider it anything more than experimental.
Also, before you judge a complex project such as an operating system, one should always consider how long it took the competition to attain the same level of completeness they are expecting.
For Windows, that would be 10 years for wireless, and then only because companies other than Microsoft did the work. Otherwise, you can move that all of the way up to 14 years ( XP ) - and that is with very poor inbuilt hardware support. But Microsoft need only worry about having the kernel boot and remain stable enough for 3rd party drivers to be installed.
For Linux, well... much longer.
Haiku has come an incredibly long way very fast thanks to 'merely' being, essentially, a reimplementation of a prior work - design decisions are mostly already made for you.
Think before you speak.
--The loon