Slashdot Log In
BeOS Ready for a Comeback as Zeta OS
Posted by
timothy
on Sun Apr 03, 2005 12:12 AM
from the operating-systems-shouldn't-matter dept.
from the operating-systems-shouldn't-matter dept.
Anil Kandangath writes "BeOS, the operating system that could have been the foundation for Mac OS X, but almost died, instead has returned as Zeta OS -- which is supposed to be fast, stable, media centric and boot within 15 seconds. Zeta is being released by yellowTAB of Germany and has applications such as an office suite and the Firefox browser bundled with it. Most BeOS applications will also run as-is. Screenshots are available." According to the NewsForge story linked there, the release could be as soon as next month.
This discussion has been archived.
No new comments can be posted.
BeOS Ready for a Comeback as Zeta OS
|
Log In/Create an Account
| Top
| 625 comments
(Spill at 50!) | Index Only
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Well, yeah... (Score:3, Funny)
Re:Well, yeah... (Score:5, Interesting)
-kaplanfx
Re:Well, yeah... (Score:5, Informative)
(http://shortcircuit.us/ | Last Journal: Sunday October 14, @02:01AM)
Well, unless you include clusters. But boot times on those are still limited by the abiltiy of each individual node.
Re:Well, yeah... (Score:5, Insightful)
(http://www.stileproject.com/ | Last Journal: Friday June 22, @03:09PM)
Re:Well, yeah... (Score:5, Insightful)
Re:Well, yeah... (Score:5, Insightful)
That's funny because I can't stand having to wait for every little thing to load before starting.
Maybe I'm just spoiled, but the difference is more startling when one uses a dual proc machine. My XP machine at work gets up to speed quickly. Almost as soon as my desktop is up, I can start loading my apps. On my laptop, I see that lag that you're describing. I'm reasonbly certain that the other processor is doing the work. Great stuff.
In any event, at least seeing that your computer is almost there is a psychological relief. Sort of like 2 minutes of commercials is usually better than seeing 2 minutes of black screen. (Which NBC likes to do here frrm time to time, don't ask me why.)
Re:Well, yeah... (Score:5, Interesting)
I call this the Disney effect. If you've ever been to a Disney theme park you typically wait about 20 minutes to get on a ride (excluding the "mountains") however they break the line up and never let you see the whole thing as well as have little pitstops of entertainment before you get on the actual ride.
I've always thought it was brilliant and was reminded of it the first time I saw Windows 2000 boot (it goes through 3 stages, NT text, then the splash, then the screen before login).
Re:Well, yeah... (Score:4, Insightful)
(http://www.jeffreysharp.org/)
For those who know... (Score:5, Interesting)
Re:For those who know... (Score:4, Interesting)
On the other hand, Mach is pretty slow, and stuffing the BSD layer into the kernel space and building everything off of it made a Mach base superfluous. Objective C is a mediocre language with expensive message dispatch, but OpenStep was a powerful platform that proved itself to be easy to develop for.
Re:For those who know... (Score:5, Interesting)
(Last Journal: Wednesday October 20 2004, @01:41AM)
Openstep is a well designed API, if not the best ever so this makes up for the ugliness of Objective-C. However, I could not imagine using Objective-C for anything but a Cocoa program.
The dispatch is rather expensive, but having dynamic binding like it does is the reason for this. This allows for great flexibility while designing software but of course comes at an execution cost. For the OOP nuts, it's pure but I agree, they could have done things better with the language. It's definitely the Achilles heal of the whole Cocoa thing and makes you guess they will have a superior Java implementation eventually.
Re:For those who know... (Score:5, Interesting)
(http://www.scarydevil.com/~peter/ | Last Journal: Monday September 26 2005, @06:53PM)
And C++ feels like Simula bolted crudely on to C, and Java feels like C++ on Prozac, and runs like C++ on 'ludes.
The REAL problem is that C is not a good base for an OO operating system. The best OO C derivitive is Livescript/Javascript/ECMAscript, and that's because it doesn't try and retain C semantics anywhere.
Re:For those who know... (Score:4, Informative)
(http://theravensnest.org/ | Last Journal: Sunday October 07, @07:05AM)
No it isn't. Take a look at the source. The Mach / BSD parts of the kernel are C, while the IOKit drivers are a stripped down version of C++.
Re:For those who know... (Score:5, Informative)
In my opinion (I've used Macs since 97 and used BeOS since the first release) I would rather have seen BeOS with the Aqua makeover. BeOS was VERY close to being like a UNIX, it tried to copy all the good stuff but left out the bad stuff.
I don't know how well it worked in a technical sense but it let you load and unload drivers and extensions just by moving them in and out of a folder (never reboot!). It also let you load extensions and drivers for the machine, or just the user (it was never multiuser but was designed with this in mind for the future).
On a 240 MHz 603e I was able to rotate a 3D cube playing QuickTime movies on all 6 sides (compressed with the "video" setting). Without GPU support. BeOS was like the new Amiga, it was amazing and would have been something truly phenomenal had it come out AFTER the DOJ trial against MS.
Re:For those who know... (Score:4, Interesting)
(Last Journal: Sunday November 04, @03:38AM)
Now I must say, for the record, that I am using OSX for most of my purposes now. Only the engineering stuff from work, like Autocad, Pro/E, and Mastercam, doesn't run on this thing. My boss told me that when versions of those programs become available for the Mac, the entire Windows-based network is going in the trash. This is cool, because seven years ago, when I told him to dump NT and use FreeBSD as his server system, he didn't believe that some alternative to Windows that he never heard of could get the job done at all, let alone do it better. Boy, did I prove him wrong after a while, but I had to make him a bet that if FreeBSD didn't do the job, I'd take him and his family out to dinner at his favorite restaurant, which is a very, very expensive restaurant!
Back to OSX and BeOS, though... There were a number of things about BeOS that I loved, including:
- Live filesystem. In other words, the operating system knows when it puts a file somewhere, right? So why poll for that information? BeOS has hooks that allow your software to install a "monitor" on a file or directory. When something happens to that object in the filesystem, your application receives an asynchronous message, and then you can act on it. Why is this useful? Someone else in this discussion mentioned that you could load a device driver just by dropping it in the appropriate directory, without rebooting. There are other reasons. Samba, for example, has an option that monitors the contents of a directory for changes, and acts on them. You have to set up how often to monitor. Samba has to maintain an internal list. This takes up a bunch of computer time. In BeOS, a simple line of code an a handler for the event would do the trick, and waste less computer time. This was cool. And it worked on any filesystem supported by BeOS.
- Attributes. This existed in BeOS long before any other OS had something like it. These things are showing up in OSX and Linux only recently. Attributes are programmable metadata that you can attach to a file. This turned the filesystem into a sort of database. The operating system had certain information that it would associate with files, such as their MIME type. This information was used to open the proper application for a file, instead of going by the file's extension. This could allow you to completely do away with extensions. Most of the time, I kept extensions on files anyway, because it was convenient for transferring them to and from other computers. But it was not necessary. You could also run queries on information, and save the query. The query could be accessed just like a directory, and it was "live" due to the previous feature I mentioned, which means that as things moved around the disk, or were created or deleted, that change would show up immediately in the query window.
- The OS was just so damn fast.
- It was built the way the Hurd should have been built, if it were ever built. In other words, there was the kernel, and then there were a bunch of "servers", like the input server, the network server, the window server, etc. Then, there were the "kits", or the APIs, that each server had. This meant the OS was so modular that you could conceivably remove any component and replace it with a better one, if the OS had ever gained widespread adoption.
Unfortunately, BeOS didn't fulfill all needs quite so well. Let's see a few things BSD has that BeOS doesn't:Returned to life.. (Score:5, Funny)
(http://slashdot.org/)
Re:Returned to life.. (Score:5, Funny)
Anything is possible [zombo.com]
right... (Score:5, Funny)
(http://www.deadkitty.org/)
Why was he learning C? Because BeOS was coming back, and they were gonna need people to port applications. And porting was easier if you knew C. And BeOS was gonna be the next big thing so they needed to have lots of apps ported to it.
If you want to take a look at BeOS... (Score:5, Informative)
Yeah, but... (Score:4, Interesting)
(Last Journal: Monday December 18 2006, @12:45AM)
Re:Yeah, but... (Score:5, Informative)
Hardware requirements? (Score:4, Interesting)
(http://www.kjwcode.com/ | Last Journal: Sunday April 03 2005, @12:28AM)
I looked over their site and couldn't find hardware requirements documented.
One thing I love about open source operating systems is that the system requirements are right there, up front -- or at least you don't have to look hard to find them.
It claims to boot in 15 seconds, which I don't doubt. It would be great to use on a laptop for that very reason. However, will my poor little laptop be able to handle it? I'd love to know before I get my hopes up.
Re:Hardware requirements? (Score:5, Informative)
Hardware requirements
Minimal Requirements:
* Pentium 200MHz (or Cyrix, Athlon, Via...)
* 32 MB RAM
* 600 MB Hard Disk Space
* 8 MB Video Memory
* bootable CD-ROM Drive
* Mouse, Keyboard, 14" Color Monitor
Recommended Hardware:
* Intel Pentium III 1 GHz (Celeron, AMD Athlon Duron/XP)
* 256 MB RAM
* 4 GB Hard Disk Space
* 32 MB Video Memory
* Soundcard
* CD/DVD Drive
* Mouse, Keyboard, 17" Color Monitor
Check our hardware compatability [yellowtab.com] list to see if Zeta will run on your machine.
Blessing in disguise? (Score:5, Insightful)
Obligatory.... (Score:5, Funny)
Whether 'tis nobler in the mind to suffer
The slings and arrows of outrageous fortune,
Or to take arms against a sea of troubles,
And by opposing end them?
Looks Aren't Everything But... (Score:5, Funny)
Way to kill it before it starts (Score:5, Insightful)
What can I do with it that I can't do with a free Linux distro, or the Windows that I already have? Tell me why I should drop $100 on this.
Re:It's all snake oil, BeOS is a dead inferior OS (Score:5, Informative)
(http://www.ranea.org/watts)
Yes, BeOS is a dead operating system. There are no marketing claims for BeOS after about 2000. If you're going to be evaluating the original claims for BeOS made during its brief moment in the sun, 1998-1999, compare those claims with what was around then, not what's around now.
Steinberg ported Nuendo [harmony-central.com] to BeOS. You'll notice that it could process 96 media tracks simultaneously. Why is this significant? Because on the same hardware the NT version could only do 48 tracks.
As a matter of fact, yes, BeOS did have a better media core than anything else did, in one specific area: latency. There was literally nothing else beyond true RTOSes that could touch it. If you go to a stage show in Vegas, Disney or even some Broadway theatres, there's a non-zero chance that the sound and lighting system is still being run by a BeOS-based system from LCS. In 2005, other operating systems have caught up in some respects, but the main thing that "beats" BeOS in media processing is simply Moore's Law: machines are so much faster now than they were six years ago that it doesn't matter that their signal processing still blows moose chunks.
There are other things that BeOS had that no other operating system had, most notably the file system and live queries that could operate on metadata. Make a virtual folder that contains all the word processing documents you've edited in the last week? No problem. BeOS was by far the most responsive operating system I've ever used. And you know what? It got more commercial applications announced for it in its first two years of public release than Linux did in its first five or six. (Some of those commercial applications are in fact still around, now on other platforms.)
Yes, BeOS had its share of problems, some of them did involve driver support, and there's been very little development on drivers since 2000. But it wasn't difficult to find supported hardware back then--I ran it on a pretty much stock Gateway PC--and I can assure you that BeOS does not suck. If Be had made some wiser business decisions (like not going after the non-existent internet appliance market, and knifing their desktop developers in order to do it), it'd probably still be around.
I'm not particularly interested in ZetaOS because, in the context of 2005, it's not a very compelling operating system. But you obviously don't have a clue why so much of the computing world was excited about it in 1999.
Re:What's the relationship to BeOS? (Score:5, Informative)
Wow... (Score:3, Funny)
(http://slashdot.org/ | Last Journal: Wednesday April 16 2003, @07:07AM)
Editors: dost thou have no mercy? From the depths of hell, the server stabs at thee!
I'm bored, waiting for the DST to kick in.. ;-)
Funny, (Score:5, Interesting)
(http://z80.org/ | Last Journal: Tuesday May 28 2002, @04:01PM)
Turned out the entire GUI crashed all the time and tons of drivers where missing. Then came a big upgrade, then another beta and then... nothing.
Now it's 2005, and it's now "ready for a release next month". I suggest they bury it instead. For good, or turn the whole thing over to the OpenBeOS people.
Re:Same failed OS, Zany new name! (Score:4, Insightful)
(http://www.scarydevil.com/~peter/ | Last Journal: Monday September 26 2005, @06:53PM)
It doesn't matter what the processor is, it just matters what the software running on it is.
BeOS
I'm more interested in the reborn Amiga OS.
Is there anything new? (Score:4, Insightful)
Re:Sadly (Score:4, Informative)
yellowTAB has just announced details of what is to be expected for Zeta 1.0. The list includes ... breaking the 1GB memory barrier"
Hee hah! (Score:5, Insightful)
(http://www.geocities.com/orion_blastar/contact/ | Last Journal: Tuesday April 03 2007, @07:19PM)
On the plus side, it should have no malware available for it.
I think Mac support for BeOS was killed when Apple refused to release info on the G3 Macs to Be, Inc. Therefore Be targeted the X86 market, hoping to save the company that way, because that is what NeXT did. Only NeXT tanked and got saved by Apple, yet Be, Inc. tanked and nobody saved it, and Palm bought out the corpse and buried it, until this Zeta Zombie rose from the dead.
I think I'll take my chances with Linux, KNOPPIX/KANOITX seems to be stable enough, boots from a live CD, and has an option to be installed on a hard drive.
I mean unless most of the major OSS projects are being converted to ZetaOS/BeOS, I think you can forget convicing enough people to buy a copy to make it worth their while.
I hate hate hate that ZetaOS (Score:5, Interesting)
(http://www.magerquark.de/)
I do work for a small German company called "zeta software [zeta-producer.com]".
Currently, yellowTab is selling the ZetaOS through multiple German home-order-TV shows to computer-illiterate persons. Of course most of them fail to successfully install ZetaOS on their supermarket-bought PCs.
A daily average of two or there of them call us (not yellowTab!) and ask what they can do, now that they crashed both their Windows installation and their ZetaOS.
Even the hints beside every phone number on our website that we have absolutely nothing to do with that ZetaOS did not help much.
yellowTab seems to be aware of the problem that many many customers seems to be very discontented with ZetaOS and additionally call all companies that seem to have the Word "zeta" in their name (which are quite a few), because yellowTab hired a marketing agency (or how you call that in English) that called us some time ago on the phone.
This agency seemed to have the task to call all those zeta-named companies and apologize for the "idiots" (= ZetaOS customers) calling them. The agency further asked us what the average questions of the ZetaOS customers was. You could call that "Indirect surveying" ;-).
I really whish myself and all zeta-named companies that yellowTab runs out of venture-capital really soon and that they disappear and never ever return again *sigh*.
Get an injuction to have the name changed then (Score:4, Informative)
(http://www.astmasters.net/maml.html)
A registered trademark is quite obviously something you have to register with the trademark registry.
A common law trademark is established through using a mark persistently. You don't have to register it.
Needless to say, registered trademarks are easier to enforce, but common law trademarks are just as valid.
Another important fact about trademarks is that there are 40+ different categories. Two companies can hold the same trademark for their products in the same country as long as they are in different categories. Since you are a software company and Yellow Tab's ZetaOS is a software product, there can be no doubt that both companies' products fall into the same category, the one for computer software.
Now, assuming that German trademark law does acknowlegde common law trademarks, then you have established such a common law trademark by trading as Zeta Software. If you can show that you have been trading for longer than Yellow Tab has been marketing ZetaOS, then you stand a very good chance that you can get an injunction to force them to change the name. The fact that you have those errant calls will actually help you to go after them.
Even if German trademark law doesn't help you, I am sure that German company law will have various clauses that protect a registered company's name from other companies in the same sector using the name.
Don't have pity for them. They should have done their homework before launching their OS. They should have never picked that name in the first place. A simple check with the company registry would have revealed that you guys exist.
On the other hand, if your company has been founded after Yellow Tab have started to market their OS under the Zeta name, then the blame would go to you guys.
In any event, you should get some legal advice from a lawyer dealing in such matters and see what your options are.
Good luck.
BeOS is here to stay... (Score:5, Informative)
http://web.archive.org/web/20010521150816/www.bene ws.com/beos/ [archive.org]
to learn the root of the OS.
BeOS was originally developed for BeBOX(custom ppc based smp box) and later started supporting 60x lines of PPC based Apple's Macintosh computers and power computing(Taiwan's mac licensed manufactural).
With version 3.0 x86 versions started shipping.
There were 3.0, 4.0, 4.5 then 5.0 Personal Edition and 5.0 Professional Edition.
I personally believe that BeOS doomed itself with expensive public relations fund spend heavily on BeOS Preview release 2(Remember those BeOS preview release shipped with Mac related magazines for free?) and decision to start selling x86 version. They started offering free version for 5.0 called 5.0 Personal edition, which were bit late(developers have migrated to linux world then...). So company were bought out by Palm.
However, right before they were bought out by Palm, there were two main project which disappeared all together.
BeIA with SONY eVilla project and Dano(BeOS 5.5 release). BeIA pretty much slipped away when Be had office equipment auction when they closed down the building along with some handheld devices(tablet computers loaded with BeIA).
I've heard rumors that after Sony seeing the utter failure of QNX based iOpner(which was immediately followed by another QNX based 3com'saudrey), axed eVilla and destroyed all produced units, so only surviving units are the ones that were auctioned off with BE office closing in CA(developer's machine?).
After BE was sold to Palm...however, BE source along with Dano was leaked over Beshare(beos centric p2p software).
So Dano(considered as unofficial release ver 5.1d0)
OpenBeOS movement started around this time.
Now OpenBeOS has changed its name to Haiku-OS.
http://www.haiku-os.org/ [haiku-os.org].
And soon people started BeOS Developer's Edition
at http://www.beosonline.com/ [beosonline.com].
And other people started BeOS http://freshmeat.net/projects/beos-max/ [freshmeat.net]
http://www.beos-max.org/ [beos-max.org].
Both BeOS Developer's Edition and BeOS Max revolves around Be's latest official release BeOS Personal Edition 5.0 + 5.0.3 upates and many new improvement which were contributed by a user community developed opensource softwares & drivers.
However, there versions which includes some unofficial released stuffs(stuffs from Dano and some controversial stuffs)
http://phosphuros.tk/ [phosphuros.tk]
You can read the article by OSnews here.
http://www.osnews.com/story.php?news_id=6948 [osnews.com]
Here are some screen shots provided by Korean BeOS UserGroup.
http://www.bekrage.net/gallery/view_album.php?set_ albumName=screen [bekrage.net]
BeOS is nice because Localization stuffs were incorporated into GUI nicer than most other OS, making easier to support different language than English, especially where language isn't based on phonetic latin based alphabet languages such as Korean/Chinese/Japanese. Thier alphabet is 8bit(or even 16bit) character based.
Currently, Haiku-OS programmers are plugging away diligently where OS is almost ready, where most of the bread and butter applications were already worked out! This is a nicer situation where applications are already there when OS still hasn't shipped, due to special current circumstances of BeOS.
ZetaOS is heavily based on BeOS R5.0.3 + Bone network(Dano style) + lots of improvement borrowed from drivers found on BeBits(opensource community of BeOS) + Haiku-OS(OpenBeOS).
ZetaOS, there are RC1, RC2, RC3, Zeta Neo(considered as RC4) a
A Floater (Score:3, Insightful)
(http://borud.no/blog/)
Why can't they go after a market where it is needed? For instance, there are more and more ATMs popping up running windows and misbehaving in ways that you didn't think was possible for such a critical system.
Obviously BeOS, or whatever the marketroids call it this week, is stable, lean, fast, and seems to support media processing well. Why not go for the upscale embedded market? Why not go for set-top boxes, portable media players etc?
No business is going to jump ship and switch from Windows, OSX, Linux or whatever they run, to BeOS as their primary desktop OS. Come on.
Screenshots are available (Score:5, Funny)
(http://www.hut.fi/u/tkyntola/index.html)
BeOS (Score:5, Interesting)
I wouldn't be surprised if it'd take them a few months or years to catch up to the current state of technology, because it's been maintained by enthusiasts ever since the company maintaining it dropped it. Even for something that was ahead of its time, it has catching up to do, both when it comes to technology and killer apps, and I guess what I'm asking is... is it worth it?
Interesting quotes (Score:5, Insightful)
If all of that works...I know a big "if"...there shouldn't any shortage of software.
Odd operating system out? (Score:3, Interesting)
Re:Say what now? (Score:5, Informative)
Re:Zeta OS (Score:5, Funny)
Apparently you were never in grade school. The next version would be "Infinity plus one and no returns."
Re:Zeta OS (Score:5, Funny)
(http://web.vorticon.org/ | Last Journal: Monday February 14 2005, @01:00AM)
Re:Zeta OS (Score:5, Funny)
Or, if it's meant for novices, GNU/Be.
Re:Zeta OS (Score:5, Funny)
Re:yes! (Score:3, Insightful)
(http://nekobox.org/)
How would the world be better off if Apple chose BeOS over Jobs? It's not immediately obvious to me.
Re:Say what now? (Score:5, Insightful)
BeOS would have been more lightweight and probably more efficient, but OS X is maturing into something quite useable. The UNIX roots of OS X have helped lure new developers and new types of users to the platform. Having more developers is never a bad thing.
BeOS would also have been a cleaner start. It's difficult to say how much (or if) UNIX is holding back MacOS X. I find OS X somewhat bloated, especially in terms of the number of files that it is comprised of. I wish it took less time to make a backup.
BeOS is/was also advanced in terms of file meta data. That situation is still quite messy in MacOS X.
Re:Say what now? (Score:4, Informative)
(http://www.pascal.com/)
Metadata is data about data. File metadata is information describing a file or its contents.
On many operating systems, file metadata comes primarily in the form of filename extensions. A file with the name "house.jpg" can reasonably be assumed to be a JPEG image file.
Unfortunately, filename extensions are pretty limited as a means of storing file metadata. There's a lot of other metadata one might want to store and retrieve for a give file.
Classic Mac OS went a small step further, storing 2 pieces of file metadata: file type and file creator. This information was stored separately from the filename, allowing Mac users to name there files whatever they wanted, without having to include a filename extension. It also allowed them to have some JPEGs open in Photoshop when double-clicked, and others to open in a web browser, by means of the files' creator metadata.
Not too much later, the World Wide Web appeared, and with it the use of filename extensions as required metadata for any files to be transferred via the Internet. So Mac users learned to live with filename extensions. Most of them were already doing so.
One development that accompanied the rise of the Internet was the development of mime types, another means of storing file metadata. BeOS used mime types extensively for storing file metadata, in conjunction with a database-driven filesystem. From what I saw, the combination was pretty effective and powerful.
File metadata on Mac OS X is a mess because Apple has officially abandoned the traditional Mac type/creator metadata system. This is one area where Apple could have taken a leadership position as they transitioned their core userbase and developers to their new OS, as they did in other areas like Core Audio, but instead of replacing the type/creator paradigm with some newer, better metadata system along the lines of that which already existed in BeOS, they simply chose to fall back to the less powerful but more internet-compatible filename extension paradigm. Yet they did not completely abandon the traditional system, as it would have made porting classic Mac apps to O S X more difficult. So some Mac OS X apps use type/creator metadata, some only use filename extensions, and some use both. Without a clear leadership direction from Apple, things are kind of a mess. Not that most users would notice.
There is some hope. Last I checked, Dominic Giampaolo was still working at Apple. He was the main brain behind the BeOS filesystem and went to work for Apple a few years back. He's responsible for the journaling support that was recently added to Mac OS X. Many folks (myself among them) are hoping that Dominic will bring the BeOS metadata system (or something like it) to Mac OS X. I believe Tiger and Spotlight will bring some improvements in this area.
Re:Say what now? (Score:5, Interesting)
the problem of storing metadata that way is that its non portable. it's exactly the same problem that plagued macos classic. great when you only deal with macs but bad when the internet comes around and suddenly you have no simple way to transport files around.
also bad when you need to talk eg nfs or smb.
storing metadata in bundles and the whole bundle system allows macos to be transparenly "native" on just about any filesystem.
linux and nt have the ability to attach metadata to files, but nobody uses it. it would be a huge pain if anyone did start, because it would then suffer from again being non portable.
osx bundles are a sort of compromise between having metadata available, but in a way thats portable. its a bit ugly, but it works.
its also all xml, woo woo.
Personally, I think it was a wise move (Score:4, Insightful)
Not only that, but the NeXT system had a significant userbase, and, more importantly, software. There was a large amount of software that was available on NeXT, some of which is still being added to OSX now (Apple's Pages software, for example, was once a NeXT app called, wait for it, Pages). Also, Next had the advantage of being used in research institutions (The WWW was developed on a NeXT by Tim Berners-Lee) and was one of the very first systems to offer a fully fledged web application server (WebObjects). The fact that NeXT also had the advantage of some 8 or 9 years of experience and development behind it didn't hurt its chances either.
Possibly, one of the additional factors in Apple's decision was the fact that basing the next Apple OS on BeOS would have meant using a completely untested system. Untested in the market, I mean. Given that Apple really was in dire straights at the time (1995-1996), I think Apple made a wise decision.
But who knows, perhaps BeOS would have made apple become the absolute killer in the OS world.
Re:15 Seconds? (Score:4, Insightful)
Most of the time my "boot up" is waiting 3 seconds for the monitor to warm up. I don't shut of the PC, just the monitor.
If you want a fast boot time, run linux and leave it running...
Linux + suspend2 (Score:3, Interesting)
(Last Journal: Tuesday October 30, @10:59AM)
Maybe that's cheating. My desktop linux takes about a minute, including time spent launching an X and a couple of needed programs.
But seriously, people, this is really just problem of bootscripts and choice of desktop. That means that I can make my OS boot in 30 seconds merely by switching to a lightweight window manager, doing a little bash programming, and cleaning out the init scripts I don't need.
Re:yes, another OS! Hooray! (Score:3)