Linked by bcavally on Mon 21st Dec 2009 17:18 UTC
Thread beginning with comment 400760
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[3]: Oh for #@&%'s sake...
by umccullough on Wed 23rd Dec 2009 02:06
in reply to "RE[2]: Oh for #@&%'s sake..."
Oh there's still activity and there will be a WiFi stack eventually once they manage to port over enough *BSD drivers to make it practical to create an interface for managing WiFi, but the fact remains WiFi has yet to be a priority for Haiku.
Actually, the reason you're not seeing any more progress in the osdrawer page for Haiku Wifi is because Colin has ported all of into the main Haiku repo now, where he's added many more drivers and infrastructure already.
http://dev.haiku-os.org/browser/haiku/trunk/src/add-ons/kernel/driv...
But anyway, he is also busy with school now, and only working on it a little bit each day. Several people have been testing the various drivers out though. Note: Still no proper WPA, etc. yet until that part of the software stack is ported/written.
RE[4]: Oh for #@&%'s sake...
by bornagainenguin on Wed 23rd Dec 2009 03:03
in reply to "RE[3]: Oh for #@&%'s sake..."
umccullough pointed out...
Actually, the reason you're not seeing any more progress in the osdrawer page for Haiku Wifi is because Colin has ported all of into the main Haiku repo now, where he's added many more drivers and infrastructure already.
http://dev.haiku-os.org/browser/haiku/trunk/src/add-ons/kernel/driv...
But anyway, he is also busy with school now, and only working on it a little bit each day. Several people have been testing the various drivers out though. Note: Still no proper WPA, etc. yet until that part of the software stack is ported/written.
http://dev.haiku-os.org/browser/haiku/trunk/src/add-ons/kernel/driv...
But anyway, he is also busy with school now, and only working on it a little bit each day. Several people have been testing the various drivers out though. Note: Still no proper WPA, etc. yet until that part of the software stack is ported/written.
Well that is a pleasant surprise! Maybe what I said about WiFi being in an Alpha2 is more right than I knew?
Still I stand by my point, which is none of us know what Haiku will be like and none of us can know what it will be like until the Haiku team begins work on R2, which freed of the need for backwards-compatibility will show us what their view of a next generation OS is really like!
--bornagainpenguin




Member since:
2005-08-07
StephenBeDoper chimed in with...
That complaint is about 7 months out of date:
http://www.osnews.com/story/21562/Haiku_WiFi_Stack_TV_Card_Progress...
Yeah, about that? Not so much...
Added by Colin Günther 2 months ago
Following reasons lead to this decision:
* prevent confusion between the old nightlies and the testing versions
* due to slow down in development there aren't anymore driver versions you could call a nightly
See: http://dev.osdrawer.net/projects/haiku-wifi/news
Oh there's still activity and there will be a WiFi stack eventually once they manage to port over enough *BSD drivers to make it practical to create an interface for managing WiFi, but the fact remains WiFi has yet to be a priority for Haiku. I would imagine that would be one of those things that will be a priority in R2, but not R1 which recall is all about BeOS R5 compatibility. Then again, they are trying to modernize where ever they can without breaking that compatibility so we could all be very pleasantly surprised by Alpha 2.
StephenBeDoper chimed in with...
While I don't necessarily agree with the article, your criticism don't really paint the full picture. While it's true that BeOS was last updated in 2,000, you also need to keep in mind that BeOS was significantly ahead of its time in 2,000 (and in some ways, in 2009 too) - thanks to Be's developers intentionally designing the OS to be as future-proof/forward-looking as possible.
That wasn't the point I was making, what I was saying is that none of us know what the true Haiku operating system will look like once the team meets their personal goal of compatibility with BeOS R5, and then begin to take the code to the future, where they really want to go! I wasn't insulting Haiku, I'm just making the point that once Haiku hits R1 and are no longer constrained by the necessity for compatibility is when I expect great things to happen. Things that none of us can imagine now, because we're still thinking about BeOS and the guys writing Haiku are thinking about the next generation...
--bornagainpenguin