First Look at YellowTAB's Zeta

← Back to Stories (view on slashdot.org)

First Look at YellowTAB's Zeta

Posted by ryuzaki0 on Monday June 2, 2003 @01:31AM from the i'm-not-quite-dead-yet dept.

Gentu writes "Great news for the BeOS fans. After Be sold its IP to Palm, many said that the BeOS was no more, but a new startup company from Germany, YellowTAB, was able to get hold of Be's source code and form the future of the never-released BeOS 6 ('Dano'), under the name 'Zeta'. YellowTAB added a lot of new goodies to the OS and brought it up to speed. OSNews features the first ever preview of Zeta with a lot of good information, along with some screenshots."

12 of 356 comments (clear)

This Just in by N3WBI3 · 2003-03-25 05:34 · Score: 5, Funny

Redhat announced tday it would skip the 9.0 release and go right to 9.1

--
A Time-Saving Hint by jimhill · 2003-03-25 05:34 · Score: 5, Funny

If it's a Eugenia Loli-Queru review it can be boiled down to this: "It's not BeOS. It sucks."

--
Learn to spell: nickel, missile, lose, solely, amendment, speech, kernel, probably, ridiculous, deity, hierarchy, versus
I love Linux 9.0! by Anonymous Coward · 2003-03-25 05:37 · Score: 4, Funny

All my friends and family use Linux 9.0, and now, Linux 9.1 is even better!
Re:I still think SuSE is better by leviramsey · 2003-03-25 06:24 · Score: 5, Funny

Mandrake dropped automatic detection of ISA cards for a good reason: ISA sucks. There, I said it. ISA sucks big fat hairy moose cock.

Join the 1990's!
here we come... by Anonymous Coward · 2003-06-02 01:34 · Score: 5, Funny

YellowTab's site traffic has jumped to the phenomenal amount of 51 GigaBytes (GB) this month. We attribute this increase to the growing interest in the upcoming release of ZETA, the next generation of BeOS.
...and /.
1. Re:here we come... by locknloll · 2003-06-02 01:37 · Score: 4, Funny
  
  let's see their next bandwidth bill... hope that it doesn't burn too much of their startup capital...
  
  --
  -- Power corrupts, but PowerPoint corrupts absolutely.
wait a sec... by Alpha_Nerd · 2003-06-02 01:49 · Score: 5, Funny

You're telling me I have to pay for my operating system??
Zeta? by h00pla · 2003-06-02 01:51 · Score: 4, Funny

Bad name. I can see Catherine Zeta-Jones sueing. But as long as they don't take her picture, they should be all right.

--
I've been swashdotted -- Elmer Fudd
And in SCO news. by MongooseCN · 2003-06-02 01:52 · Score: 5, Funny

SCO declares that YellowTABs OS "BeOS" is infringing on SCOs IP. According to SCOs CEO Darl McBride: "We ran the BeOS through a machine code debugger and found sections of 10-15 instructions that are the same as those used in our product." SCO says that people need to stop using the new BeOS or face lawsuits.

Darl McBride also said that if YellowTAB were to buy a larger license, like the Entire-SCO-Company "license", the problem may disappear. When asked how a fledgling startup company like YellowTAB could buy SCO, McBride replied: "Right now even a few dollars is better than a counter lawsuit, besides I have my golden parchute. Hahah. Wait, is that tape still recodi...."

--

Outdoor digital photography, mostly in New Engl
Re:OpenBeos by bunyip · 2003-06-02 01:53 · Score: 4, Funny

Yeah, we all love the idea of open Beos...

But maybe there's at least 10 or 15 lines that look vaguely like some code SCO that probably took from BSD in the first place.

I wonder how much SCO could extort from the Beos community? Gotta be at least $3.

Alan.
Re:Looks interesting... by Timesprout · 2003-06-02 02:26 · Score: 4, Funny

some mention of why Be is better than Windows/Linux/BSD/sex/God.

Actually since I met Eugenia at a party one night she has taken sex out of that list.

--
Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
What truth?
There is no dupe
Re:Looks interesting... by Bish.dk · 2003-06-02 02:50 · Score: 5, Funny

I used to code for BeOS : the API was stunningly easy to learn.

... And not without humour. I remember a function named isProcessorOnFire(). There was a quite detailed description of when it would return true in the API-reference. Apparantly, smoke coming from the processor was not enough to warrant a return-value of true. :)