Linked by Thom Holwerda on Wed 9th Jan 2013 10:33 UTC, submitted by Straylight
Permalink for comment 547961
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2006-05-30
No, it was "announced" in October 1995, the first 100 developer boxes didn't ship till 1996.
Or 133MHz... the 133's are the ones still worth having. The 66's are horribly underpowered.
This implies to me it was just a magic drop in OS for the Mac, when clearly it wasn't. It was a hard slog. But, the Mac port was well established by the time hardware production was dropped. Mac's ran a version of DR8, after all. I had a copy of PR1 that would boot on Mac or BeBox.
That's very apologetic with regards to BeOS... truth was, at the time the OS didn't meet the specs and Openstep was far closer. BeOS was also hampered by some of the internal code - given it was either licensed from a third party or shady GPL usage.
You can also never underestimate Steve Job's power of sales, once he got wind of an opportunity.
Yes - personal version. With giant restrictions. Like not supposedly being able to be installed to a real partition (as that was actually a selling point of Pro.) The fact that droves of users used the partition install loophole was only a minor part of the reasons Be Inc failed. Because...
NO! Total fantasy. Thom and I are now screaming, "FOCUS SHIFT!!"
What really happened:
Web Appliances became a buzzword, everyone circa 1999 - 2001 was trying to launch some kind of net enabled appliance - be it a semi computer or tablet or toaster. Be saw this, decided to change focus and create BeIA, BeOS for Internet Appliances. Except, that failed dismally because no average consumers actually wanted the overpriced underpowered boxes and Sony bailed on BeIA almost before the eVilla was released. Compaq did the same thing with the Cliper. And the WebPads all later shipped with WinCE.
Secondly, BeIA is NOT BeOS. BeOS is NOT BeIA. BeIA shares a lot of the core OS with BeOS, but it is as like BeOS in reality as iOS is to MacOS X. There's a compatible API in the earlier builds (I've personally seen a lot of pre BeIA 1.0 builds running, and played with the dev kit.) BeIA did a lot different. It had a compressed file system (CFS), it had a special kernel that allowed ELF executables to be compressed (CEL format), which then used a master symbol table to uncompress the exe to run it. It was a bunch of extra drivers, such as touch screen and wireless. I personally owned a DT300 webpad and it ran BeIA from a 16MB CF card (yes MB, not GB.) The browser was the main app - Wagner (an Opera 4 based monstrosity) and there were COM like abilities and various cool comms features in the underlying OS (i.e. Binder.) Yes, one could trich the OS in to booting to a severely limited and very crippled Tracker, but it didn't really work very well and wasn't all that useful.
I'm not going to go on, but just that alone made me sceptical of the rest of the article.