BeOS For Linux
Bob Gortician writes "The BlueOS guys have posted a few screenshots of their progress in porting the BeOS interface to Linux. Note that this is an intermediary step toward a BeOS clone OS. " I actually had a Be machine for a while, and played with it - nice OS, and well thought out, just a problem of very little applications for it.
Please go to BeNews and read the explanation for these two BlueOS screenshots. The second shot uses a "dummy" content for its windows.
Also, click here to read the Interview with the BlueOS project leader at OSNews.
Driver support. Had virtually no video or sound support, so everything was in grey and mute. I loved the interface, and it booted up as quick as can be, but there's only so much you want to do with no driver support. Why make an application when no one else has a machine it'll run nicely on?
Not that the majority of Linux users care about the Mac, but the fact is that Mac OS X represents something I believe a whole bunch of Linux users should get behind if they want their OS to succeed - It's Linux with the useability that Joe Sixpack can handle. BeOS has its uses, but aside from the glory hack of porting its interface to Linux, I'm afraid that this can only serve to fragment the already small effort behind pushing Mac OS X as Linux's true way to combat Windows, because let's face it - Neither KDE nor Gnome are going to make my mother leave Windows anytime soon...
"Mod, mod, mod...and another troll bites the dust."
If it were the other way around a lot of us would probably be running BeOs on an Alpha chip right now.
The developing of a BeOS clone via this route may yield atleast the se two main benefits:
* Linux and other *nix's will gain another easy to use, mature, comprehensive GUI.
* BeOS will gain from more exposure and may get new development.
This is a great way to continue this great product.
"UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things."
just a problem of very little applications for it. Why were the apps so small?
Did it help to have a bigger monitor?
When you iconify a very little application, does it disappear?
Jeez, no wonder BeOS failed.
No one would write a lot of apps until it had a larger user base, no user base would be generated until it had more apps.
It's the same set of problems Linux has faced in the past. BeOS was/is a fine OS, but it never seemed to have a good backer, nor a solid niche. Artsy types already prefer Macs, so it's hard to compete there. Ordinary desktop users have already been won over by Microsoft, so it's really hard to compete there. Linux users already had a free OS and a nice looking desktop if they wanted it (re: KDE, Gnome. You should know that by now).
I think that BeOS was a nice, stable OS that could have been a contender. It's a shame it didn't get more press or attention from major industry players. Oh well, I look forward to another nice Linux desktop all the same.
My sigs always suck.
That's why I prefer Windows, where all my applications are *huge.
-- @rjamestaylor on Ello
The project leader is Guillaume Maillard. It's hosted at blueos.free.fr. I'm going out on a limb - the guy speaks something other than English as his native language?
While BeOS had a nice GUI, its read strength was its highly efficient threading model, which made the OS very effecient and responsive. The OS was especially adept at efficiently utilizing multiple CPUs.
While it is certainly nice that Linux users will have the opportunity to benefit from a nice new GUI and API, the best part of the OS, alas, is being left behind...
*** Quantum Mechanics: The Dreams of Which Stuff is Made ***