“From my perspective the work being done by OpenBeOS is amazing and the concept was acceptable last year. Zeta has changed the landscape now and their approach, offering backwards compatibility but trying to move BeOS forward as Zeta is a good one and with luck they will succeed. My only question is whether they’ve gone far enough to warrant the interest they hope to attract.” Read the editorial at BeOSJournal, written by David Reid.
Editorial at BeOSJournal: The BeOS Landscape
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
this guy is great, i hope he’s doing some development for one of the new BeOS-like systems
first this exellent piece by some early beos developers :
http://ralf.alfray.com/perso/powertexte.html
second : this one
http://www.labeille.net/items/FAQBeOSIntel.html which turned out to be true.
The real problem I see with beos “clones” and other projects is the number of projects available, too many for to few developers. So each project rewrite’s a befs clone, the time spent on rewritting would have been better used in debugging the firts implementation ready. Same thinsg some projects are advanced on one field while other are on others. Projects should join. Note that the summer break approching those project should be lurking for CS student willing to use their summer time to code.
btw while I’m on my beos thread, the exellent site http://www.bebox.nu has been updated with lost of imformation on Be INc’s history and the bebox. If you own a bebox check them out specially the registry page.
—
http://dmoz.org
David used to work on OpenBeOS Network Team. He stopped and explained it in his diary at advogato.org. He is a member of the sequel project too (this was available on their web page before they removed it), but with frans gone, where the fture of sequel ? sequel join merge with Open BeOS.
ludo
—
http://iceland.vefur.is
He could probably write some stuff for the OpenBeOS newsletter.
One of the most well written (and shortest) articles I’ve read in a while. Be was great, but it was getting on a bit. A lot of the time Be fans (includin myself) overlook its faults and prefer to focus on what it could have been under the right market conditions and with a better (larger – Be had gret programmers, but not a lot of them) development team. Be had/has one of the best technological bases around and its a pitty that a company with some cop on (maybe Microsoft or Apple) didn’t end up buying it for the steal of $12 million in stock.
Is anyone doing a BeOS-like API layer for X11/Linux? A separate-from-any-other-project, clearly licensed (yes I’m looking in your direction B.E.OS) Free project?
That would rock. Nay, rock isn’t a strong enough expression; it would kick butt and take names. A *modern* C++ API for linux/X. I’m getting started using wxWindows (no templates, exceptions, namespaces, or STL — yikes!) and had a peek at fltk2, but if there was a BeOS-like API lib available, it would be mighty hard to resist. Mighty.
Any X programmers out there interested in becoming heroes and receiving eternal adulation from the teeming masses? Bueller? Bueller? Bueller?
How could they? They haven’t released anything, yet. When they do, however, yes, once they do, the “landscape” might be changed, but I doubt very drastically.
Zeta will really have to prove themselves, especially, if/when openBeOS is released. Many people say that Sun will go away, because there is free linux distros available. Couldn’t the same be said for Zeta and openBeOS?
We were all burned, even though we knew it was coming, by Be, Inc. I don’t want to let YellowTab to the same thing to me, again. That’s not to say I won’t support them, because I will, and I will buy a copy of it, once it’s released. But, once openBeOS is released, I highly doubt that I will buy another Zeta release again, that is, unless they really make something worth wild, and, is compatable with openBeOS.
-paul
Does anyone know what the min system requirement would be to run one of these ‘BeOSes’. Would it be possible on a Pentium1 (100mhz) laptop, or a 266mhz Desktop?
It’s called blueyedOS …
—
http://www.abisource.com/~hub/
266 would be fine
—
http://www.zob.org
There is no such thing as a modern C++ GUI library. Qt is very similar to BeOS’s API, but both are classic C++, in that they don’t use the STL (in fact, many classes don’t even work with the STL), don’t use templates, etc. There was discussion of a modern C++ GUI library on comp.lang.c++ a month or so ago, you might be interested in looking that up.
I won’t post the link here, because it would be so long as to mess up the page formatting, but search Google Groups for “Modern C++ gui library” and look at the first three hits.
It is called BeFree.
It doesn’t require _only_ X11 but the first driver will be based on XFree because it supports a lot of graphic cards.
http://befree.berlios.de
Check out Qt, not Be’s API, but damn nice c++ API to work with…
arougthopher wrote:
> We were all burned, even though we knew it was coming, by Be, Inc.
Right on the money arougthopher. Say, you’ve gotta get an easier-
to-spell nickname.
Ludovic H. wrote:
> It’s called blueyedOS …
That’s who I was referring toward in my OP as “B.E.OS”
Rayiner wrote:
> There is no such thing as a modern C++ GUI library.
Not sure, but I think fltk2 is maybe getting there…
> Qt is very similar to BeOS’s API, but both are classic C++
Right. Though, I was careful to say “BeOS-like” in my OP.
> in that they don’t use the STL (in fact, many classes don’t
> even work with the STL),
Huh? You mean the API’s classes have problems with stuff like
std::list<API_Widget> widget_list;?
> There was discussion of a modern C++ GUI library on comp.lang.c++
> a month or so ago, you might be interested in looking that up.
Thanks.
Interesting thread. Hmm… not one mention of fltk2.
Pier Luigi Fiorini wrote:
> It is called BeFree.
> [snip]
> http://befree.berlios.de
I don’t see much at that url. The “a” directory has the beginnings
of a page there, but there’s no faq or docs, so I can’t tell what
berliOS or BeFree is.
Last night at 2 AM I ran a crontab that does cvs export in htdocs/ but something went wrong.
Now it should be ok.
BerliOS, if you don’t know it, is a sort of sourceforge.net.
I haven’t heard anything about Zeta or OpenBeOS having higher min. requirements than the original BeOS, which merely required a Pentium or higher processor (wouldn’t run on a 486).
I currently run BeOS Pro 5.0.3 on a 200Mhz desktop.