And more Haiku news; Ars took a short look at Haiku. “As an open source enthusiast and former BeOS zealot, I’m very excited to see Haiku reach this level of usability. I look forward to the day when it is a viable operating system for day-to-day use, and, when it achieves the requisite level of hardware compatibility, I fully intend to install it on my Eee PC, where Haiku’s extreme responsiveness and fast boot time will be of significant value. Although Haiku and its technologies aren’t quite as relevant today in the face of more modern and advanced operating systems, many of the traditional advantages of BeOS that are present in Haiku still have value today in some contexts.”
Ars will have to wait until this is fixed:
http://dev.haiku-os.org/ticket/1671
Nice short overview/review.
That desktop looks so damn clean and crisp.
“i-likes”
Cant wait for the first release of Haiku.Oh,made me chuckle to see his processor well over 2GHZ but the ram count only @ 256.Impressive I say.
Two thumbs up.
I imagine 256MB was all the author had allocated VMware Player, but who needs more than 256MB when Haiku’s only using 89MB, anyway?
Yeaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa!!!!
When I saw that I had to get a crane to pick up my jaw it fell that quickly and that low. I look around today, people whimsically flinging their hand going, “ah, who cares, 100mb here, 100mb there, it doesn’t matter!”. Its nice to see that the availability of gigs at disposal hasn’t gone to the developers heads.
Personally, just between you and the rest of the forum, i think that HaikuOS has a lot better chance of challenging Windows on the desktop than Linux has. HaikuOS has a completely standardised setup from the ground up, a stable driver development kit, a great application development kit, a GUI which is easy to use and eye pleasing. It has everything going for it.
In terms of performing as a desktop operating system I agree without reservation. As a by-product of its very nature, I don’t think Linux will ever be entirely fit for the desktop. The amount of messing around I’m having to do at this very moment in order to simply install VMware Player really reiterates that to me.
That said, I can’t help but feel Linux has too much corporate support for Haiku to ever really trouble it, let alone Windows.
I really hope I’m wrong and acknowledge that there are a lot of people out there who desperately want a viable alternative to Windows, something which through the virtues of BeOS, Haiku has already proved it can be. Compared to Linux even today, BeOS was effortless in my experience, with my only qualm at the time being a lack of support for my sound card.
“As a by-product of its very nature, I don’t think Linux will ever be entirely fit for the desktop. The amount of messing around I’m having to do at this very moment in order to simply install VMware Player really reiterates that to me.”
Well, no OS is ready for the desktop, if you don’t want to do any setting up.
I don’t even want to *think* about all the work that needs to be done on a fresh installation of Windows XP to make it halfway decent. Dozens, if not hundreds, of settings scattered all over to change; hundreds of megabytes worth of updates; dozens of programs to install since virtually none of Windows’ stock programs are worth using IMO; restart, restart, restart; defrag the drive because by now it’s probably running like a slug.
Sure, some things *are* easier in Windows to the point of being a breeze, as your example of VMWare (which I have yet to get VMWare Server running in Linux myself), but really… can Linux really be at fault? Shouldn’t it be the sole developer and maintainer of the program, VMWare? Surely they could, for example, at least provide a .deb file in addition to their .rpm (which never worked for me either) and bare .tar.gz.
Now we also have the Auckland Layout Model:
http://www.cs.auckland.ac.nz/~lutteroth/projects/alm/
I havn’t played much with it myself yet, but it really rocks.
I wish I could mod you up more for pointing out the stupidity of, “My 16-core, 64 GB or RAM, 2 terabyte RAID 15 setup will be the norm… someday… maybe in the next century.”
I’m not saying it won’t happen, we shouldn’t push the boundaries, or software shouldn’t evolve, but I would like to see a little more efficiency in the programs I use.
It’s pretty amazing what can happen when the entire kit is intelligently designed from the ground up.
I’d love to see how Haiku performs on an Eee! (HINT!! HINT!!)
EDIT– damn…kvdman posted a bug preventing it from even booting up…
Ohh I don’t know about that… BeOS was designed to offer the best real time performance and in my humble opinion that showed in how it ran. As long as the people behind Haiku retain that part of the BeOS’ heritage I don’t think they’ll have any problems. What many people seem to forget is how much BeOS influenced other OSes to improve their latency, just by showing it could be done.
–bornagainpenguin
Edited 2008-02-12 22:03 UTC
Haiku on the Eee PC – I think I’ve just seen my personal mobile computing heaven 🙂
BeOS really did a good job of making low powered hardware responsive; it booted crazy fast, it looked pretty, it acted like a modern solid desktop OS should.
Combining that with the Eee would be awesome 🙂 Expanding on that thought slightly, lets all hope and wish really hard that a hardware vendor thinks this too: with the new trend in cheap, lightweight, tiny laptop-like devices, software is one place where manufacturers can differentiate themselves. Imagine a hardware developer contributing to Haiku and shipping it as the native OS on a micro laptop, UMPC or internet tablet. Now pick your tongue back up off the desk
I have Mandriva 2008 on there but haiku will scream on it. I hope that one the core system is out Driver devs flock to it… I also hope that the Haiku devs made it easy to port a Linux driver over.
I’m not sure if you have a realistic time scale about Haiku’s development. Maybe — if we are lucky — we’ll have Alpha 1 this year, but I wouldn’t bet on it.
No, they didn’t. There’s a source-level compatibility layer for FreeBSD network adapter drivers and there’s an Open Sound System port (as a plug-in into Haiku’s sound architecture) that provides support for additional sound drivers. Both were probably chosen for its license because GPL stuff is not welcome in the core OS. Haiku’s license is the MIT License. FreeBSD’s 2-clause license is basically the same as the MIT License and when OSS was ported, it was under the “non-viral” CDDL. Since a while OSS is also BSD licensed which fits Haiku even better.
AFAIK Syllable offers limited source-level compatibility with Linux drivers but I could be wrong.
I would be surprised if we don’t see an alpha release before the end of the year. I suggest you take a look at the alpha milestone on Haiku’s Trac. There’s still work to be done, but a lot of progress has been made over the last few months. Self-hosting was the main requirement for an alpha release and if yesterday’s story was any indication, it’s a goal they’re very close to accomplishing.
I’m sorry if I sound negative but I’ve read similar statements for the last two years.
“I’m sorry if I sound negative but I’ve read similar statements for the last two years.”
Reading and seeing are two different things. I just used r23948 (the latest RAW version over at Haiku’s website) and was quite impressed by how unstoppable it was. I had 10-12 apps all going at once and even tried copying a 1.7Gb folder at the same time. It just kept on going! The CPU usage never went crazy (massive slowdown) and the overall system seemed quite responsive no matter what I did!
Haiku has taken a long time (many years) to get to where it is today, but… to those, like me, who cherish each new perceivable bit of progress we can see and feel, it is well worth it.
Keep up the good work, boys… Haiku’s beginning really pick up steam!
OSS is multi-licensed. It’s under BSDL, GPL and CDDL. Strangely Haiku specifically uses the GPL, not CDDL/BSDL or multi-license. I asked in late January on the haiku-development mailing list why the GPL is used. I never got a reply. I don’t know how the various parts of Haiku are connected internally but this could mean that Haiku is currently under GPL due the GPL’s viral nature.
Syllable Server (uses a Linux kernel) has full Linux driver compatibility.
Please don’t spread FUD like this…
The OSS port isn’t officially in the Haiku repo. It wasn’t really an official Haiku project. In the repo, there is essentially a media add-on module that translates from OSS to Haiku’s media kit and reviewing all the source files, it is MIT-licensed code (not derived from OSS). The OSS port is actually a zipfile download of binaries that can be installed separately when you build Haiku (see the UserBuildConfig.sample). You clearly opened the text file in that directory and simply jumped to conclusions (when a quick glance at the code would have shown you the license).
In any case, the person to contact is mmu_man (Francois Revol) since he’s the one that ported OSS.
And finally, even if the GPL OSS code was in the repo – that doesn’t automatically make the entire OS GPL – you should maybe do some research on how this works. There *is* in fact TONS of GPL code in the repo…
Which part of “I don’t know how the various parts of Haiku are connected internally” do you not understand? Stop accusing me of spreading FUD. Mkay? If I wanted to spread FUD, I obviously wouldn’t confess my limited knowledge first.
The file “src/add-ons/media/media-add-ons/opensound/OpenSound_README.txt” in the Haiku source tree says:
“Released under GPL.”
I asked a legitimate question on the haiku-development mailing list about what’s the deal about this line and why the license change of OSSv4 is not reflected. When nobody answers me, it’s not my fault.
Maybe the version used by Haiku is still the old, pre-license change version? In other words, does the license change work retroactively?
The port is older, but as long as the code is identical, there’s no problem.
It doesn’t matter, there is no code in the Haiku repository that is licensed from OSS. That’s the whole point here – the original premise that Haiku repo actually has any code ported from OSS is wrong to begin with.
Spreading FUD is not always a conscious decision. In my opinion, it’s irresponsible to start throwing around license issues and concerns when you don’t understand the circumstances.
It’s even worse to do it in the comments of a public news article completely unrelated to the topic at hand.
In my opinion, it mostly appears that you’re just annoyed that you didn’t get a response on the mailing list when you asked – which isn’t my fault.
Did you miss this part at the TOP of the same txt file?
In any case, I’m just ranting now, sorry if I offended you by trying to negate your seemingly-negative comment in the first place.
edit: removed Francois’ email address to reduce possible spam
Edited 2008-02-13 17:39 UTC
You’re right. It’s mostly useful for network card drivers.
latest build: http://www.thecodingstudio.com/opensource/linux/screenshots/index.p…
Yes! And Duke Nuke Forever will also rocks! … in 10 years. I hope Haiku will be ready by then.
I read that 3DRealms is currently aiming at fall 2008 for the DN4E release. When Haiku 1.0 is ready by then, I’m happy.
Glad to see the Network Kit is usable. Haiku is making great progress.
http://matthewsheffield.blogspot.com/2008/02/firefox-on-haiku-scree…
I don’t how you did it but I would be more than happy to run Haiku + firefox wirelesly. awesome!
-2501
I have noticed, the scrollbars are different than the original BeOS but I saw this when I used it last time otherwise it is a very promising OS. I like the look and the feel of BeOS.
Edited 2008-02-13 08:03 UTC
Thankx for taking the time to write this review of the state of the project as well as for the pics!
This is very very exciting and I’m hoping that within a couple of years it will be worthy of it’s own partition!