Haiku Project Announces Availability of Haiku R1/Alpha 2
haiku-os.org
haiku-os.org
Especially for hardware support it would be kinda nice if more projects would use a common kernel instead of writing one themselves, and I find it also hard to believe that its easier to write a new kernel (that actually works in a range of hardware) compared to modifying an existing kernel to fit the project.
There are an abundance of 'niche' distributions (focusing on size, audio support, etc) but none that really attempt new things. Actually, I'm sure there are some more but I haven't heard of them.. please inform me.
But of course, why are we complaining instead of thinking up possibilities of our own?
I've known about the project for quite a while, pretty icons and whatnot, but never fired up a vmware-like program to install it and check it out.
There's some things not like they should be. This alpha is missing vi and ed (and no 've' either). It has nano. It has gcc and python2.6 and a perl5 though. Python libraries seem to work.
In some ways it's further ahead than Be. For example - far better web browser than was ever available back in the day (even relative to web browsing standards of the time). Could use some polish, but still a remarkable achievement. Better email functionality, although parts could be implement a lot better.
Little things are not right - keyboard shortcuts and the like. But it's much better than I was expecting on this front. People have definitely been putting energy into quality. A lot of little things work like they should that I've tested.
I'm using it under vmware on a macbook. The 'tracker' interface still feels way better to use than anything else I've used (including current-era finder).
I was a die-hard user, and it's quite novel to think that - long after having given up on the dream of being able to run this as my primary workstation OS - I may be on the brink of being able to do just that. The key will be whether it can be installed natively with all drivers working effectively.
Update: dell lat. gets a good pass on compatilibity: http://www.haiku-os.org/community/forum/dell_latitude_x1_dre...
I guess I should have clarified - I've never used BeOS either, or well, even seen it I think, so more detail would be interesting, but from what you're telling me so far its not in a very usable state, but nonetheless I'm curious, might install it some weekend.
Try navigating around the filesystem quickly by right clicking on the desktop (holding it) and then following the directories. If you want to open one, just put the mouse over it and lift.
Something that didn't get much press but which is unique and wonderful to use is the integration between the filesystem and the UI. Email messages are just files that sit in a directory, but the tracker exposes attributes to them, and you can have it display columns for 'From' and 'Subject'. Your inbox is just a folder that contains your mail messages. There's an instant message client that works along these lines too. Users are just files, and the IM functionality is a plugin engine to the tracker. This feels connected to the 'everything is a file' philosophy.
The OSX filesystem is technically capable of some of this stuff (written by the same guy, and later, so it's probably a lot better), but the finder isn't. So even though OSX is probably superior internally, in practice it isn't better to use.
There's a library called bethon that exposes the internals of the OS to python. I've used this with success in the past, not recently. It used to be the case that you could use a combination of the C++ BeBook dev but then piece stuff together from the python console.
Update: Got bethon working. It's a bit of a fiddle in this VM because there's limited disk space available, and sed isn't linked in /bin. But once you get it built the example at http://donn.drizzlehosting.com/Bethex.html works fine.