Things are now really starting to get interesting. Rudolf with his drivers which makes Nvidia cards run smoothly, the Haiku kernel slowly maturing, the app server close to completion and many many limitations removed…
I can’t wait to get that first .iso when it arrives…
I think it would be better to say the year it starts getting interesting, from a visual standpoint. There has been lots of progress, but now we are starting to see some visuals(and we all love visuals) where it starts to feel more like BeOS.
Getting something Visual working is a big step. Until ReactOS got to that point almost nobody believed in it. But afterwards people got more enthusiastic and ReactOS got some extra developers. I see something similar happening to Haiku this year.
It’s interesting to note the momentum in all things Haiku related, ever since the kernel became bootable from hard disk. If you check the daily SVN log, there is a lot of GUI development happening these days, and it’s only really a question of weeks before a self contained version of the app server is running. Once Haiku is able to be buildable and editable from its own environment, expect enormous (daily) progress reports from all the teams, who finally have the last peices of the jig saw to put together.
And then the fun starts ….
2005 – Haiku developers have something nice to play with.
2006 – Old BeOS users have something nice to play with.
2007 – Disgruntled Linux users have something nice to play with.
2008 – Disgruntled Windows users have something nice to play with.
2009 – Year of Haiku. 1% marketshare. Bliss.
No, I’m not being sarcastic. I think that 1% market share is amazing, this day in age. It’s just large enough to get native drivers and enough quality native apps, and a substantial community involvement, enough to be sustainable.
If Haiku gets 1% market share by 2009, it can be considered a smashing success, considering that most likely until that timeframe, Haiku will have no major commercial support (like Linux had with IBM, and FreeBSD with the web).
hmm, haiku development is on very rocky road now IMO; i hope that those guys will not give up and some day we will be able to download the first complete haiku iso(i do not mean beos r5 with haiku parts in it ^_^).
===to_haiku_team===
good luck! and realize that there are many people believing in your success(and often they cannot code so cannot help you writing it :|).
No, this won’t make it easy to port Unix/Linux stuff. BeOS was somewhat Posix compliant, but some Unix apps use OS specific extensions (the BSD guys complain about lots o apps using Linux specific code).
What this means is that the Haiku guys will have a heck of an easier time testing their stuff. Not having to reboot for testing every app and all.
2005 – Haiku developers have something nice to play with.
2006 – Old BeOS users have something nice to play with.
2007 – Disgruntled Linux users have something nice to play with.
2008 – Disgruntled Windows users have something nice to play with.
2009 – Year of Haiku. 1% marketshare. Bliss.
To be honest, I’m not sure it’ll take that much time, even though very much point to the fact that things do take time. So many things though might make this happen faster. For instance, the Linux effect, meaning a big part of computer users are actively looking for alternatives to MS. For most the only one there has been Linux, which many also admit are lousy for the desktop. I believe that a huge amount of these users will switch for Haiku for desktop use and keep Linux for their servers…
There’s no real relationship between Haiku and YellowTab apart from several Haiku dev’s now work for YellowTab. YellowTab I believe, are using some of the completed Haiku modules.
This is great! I believe now that we can boot into a shell, development is just gonna be that much faster. The more components that we can bring up, the more of the system that is ready, the faster development goes. Once we get gcc and the rest of the dev toolchain working, then things will start to get interesting.
It may very well be this year or the next that haiku-r1 will be released in my opinion, or at least this is the impression I’m getting, because it seems that progress is being made exponentially faster than before. Or maybe it’s that I saw a screenshot after all this time! The kernel is able to boot, the app_server is running on the kernel, and apperantly the input_server is too! This is very exciting for anyone who has been watching this project for so long.
cant wait to use BeOS and its decendants again.. Good work guys..
Things are now really starting to get interesting. Rudolf with his drivers which makes Nvidia cards run smoothly, the Haiku kernel slowly maturing, the app server close to completion and many many limitations removed…
I can’t wait to get that first .iso when it arrives…
Brilliant work Michael and all the others
I think it would be better to say the year it starts getting interesting, from a visual standpoint. There has been lots of progress, but now we are starting to see some visuals(and we all love visuals) where it starts to feel more like BeOS.
Congrats to the Haiku team.
Getting something Visual working is a big step. Until ReactOS got to that point almost nobody believed in it. But afterwards people got more enthusiastic and ReactOS got some extra developers. I see something similar happening to Haiku this year.
It’s interesting to note the momentum in all things Haiku related, ever since the kernel became bootable from hard disk. If you check the daily SVN log, there is a lot of GUI development happening these days, and it’s only really a question of weeks before a self contained version of the app server is running. Once Haiku is able to be buildable and editable from its own environment, expect enormous (daily) progress reports from all the teams, who finally have the last peices of the jig saw to put together.
And then the fun starts ….
2005 – Haiku developers have something nice to play with.
2006 – Old BeOS users have something nice to play with.
2007 – Disgruntled Linux users have something nice to play with.
2008 – Disgruntled Windows users have something nice to play with.
2009 – Year of Haiku. 1% marketshare. Bliss.
No, I’m not being sarcastic. I think that 1% market share is amazing, this day in age. It’s just large enough to get native drivers and enough quality native apps, and a substantial community involvement, enough to be sustainable.
If Haiku gets 1% market share by 2009, it can be considered a smashing success, considering that most likely until that timeframe, Haiku will have no major commercial support (like Linux had with IBM, and FreeBSD with the web).
Haiku does already have commercial support. YellowTab is using pieces and bits and will do even more so in the future.
Oh, and your roadmap sounds a bit like what the ReactOS guys thougt when they had their first beta release:
October 2004
* Extensive Library content
* Collaborative development with Academic and Government institutions
April 2005:
* Usable as Home and Business Desktop platform
* Usable as Small Business/Non-Profit Server platform
Wow, them guys on the Haiku team are just chugging along. Good work, can’t wait to see what the future holds for this project.
hmm, haiku development is on very rocky road now IMO; i hope that those guys will not give up and some day we will be able to download the first complete haiku iso(i do not mean beos r5 with haiku parts in it ^_^).
===to_haiku_team===
good luck! and realize that there are many people believing in your success(and often they cannot code so cannot help you writing it :|).
Does this mean that it will be very easy to port things from Linux and Unix such as OpenOffice etc.?
No, this won’t make it easy to port Unix/Linux stuff. BeOS was somewhat Posix compliant, but some Unix apps use OS specific extensions (the BSD guys complain about lots o apps using Linux specific code).
What this means is that the Haiku guys will have a heck of an easier time testing their stuff. Not having to reboot for testing every app and all.
And then the fun starts ….
2005 – Haiku developers have something nice to play with.
2006 – Old BeOS users have something nice to play with.
2007 – Disgruntled Linux users have something nice to play with.
2008 – Disgruntled Windows users have something nice to play with.
2009 – Year of Haiku. 1% marketshare. Bliss.
To be honest, I’m not sure it’ll take that much time, even though very much point to the fact that things do take time. So many things though might make this happen faster. For instance, the Linux effect, meaning a big part of computer users are actively looking for alternatives to MS. For most the only one there has been Linux, which many also admit are lousy for the desktop. I believe that a huge amount of these users will switch for Haiku for desktop use and keep Linux for their servers…
Feels good, my dream is Linux & BeOS for X86 (no more windows)
Don’t forget USB support coming soon. That should be interesting.
Does anyone know the status of java Runtime under BeOS? Isn’t OpenOffice a Java creation?
I would love to see a review of YellowTab. Is it for sale commercially yet??
can someone please spell out the relationship between YellowTab and Haiku?
There’s no real relationship between Haiku and YellowTab apart from several Haiku dev’s now work for YellowTab. YellowTab I believe, are using some of the completed Haiku modules.
This is great! I believe now that we can boot into a shell, development is just gonna be that much faster. The more components that we can bring up, the more of the system that is ready, the faster development goes. Once we get gcc and the rest of the dev toolchain working, then things will start to get interesting.
It may very well be this year or the next that haiku-r1 will be released in my opinion, or at least this is the impression I’m getting, because it seems that progress is being made exponentially faster than before. Or maybe it’s that I saw a screenshot after all this time! The kernel is able to boot, the app_server is running on the kernel, and apperantly the input_server is too! This is very exciting for anyone who has been watching this project for so long.
why do developers these days insist on using tiny, blurry antialiased fonts?
call me a luddite if you like, but i hate them.