Review of BeOS Developer Edition 1.1 222
TweetZilla writes "Good review if you are a fan of BeOS. Not ready for regular users but tinkerers will probably love it to death.
OSNews is carrying the story."
The sooner all the animals are extinct, the sooner we'll find their money. - Ed Bluestone
I thought BeOS died... (Score:1, Offtopic)
OS/2 is dead. . .Long live eComStation! (Score:2, Informative)
Be... (Score:3)
Re:Be... (Score:5, Insightful)
For one thing, developers wouldn't be able to look at the source, because it would taint anything they would put out.
More importantly, the BeOS relied on a lot of proprietary, third party components. The BeOS developers pretty much said that it would be virtually impossible to disentagle the proprietary stuff from the Be stuff. Even if that were possible, you wouldn't have anything useful.
Besides, the Open BeOS [sourceforge.net] is making good progress without the source code.
Wait a second..... (Score:2, Insightful)
Be was great design (Score:2, Informative)
Re:Be... (Score:1)
tinkerers will probably love it to death (Score:4, Funny)
I never consider trying it (Score:2, Insightful)
It came with lots of GNU software, which i found great since they are free (as in free speech), then i read even more.
It has terminals, which i did not knew it had.
This will definitely be something i will try in the future.
Re:I never consider trying it (Score:3, Interesting)
Re:I never consider trying it (Score:2)
dead in the water
I love OS/X as much as anyone, but I just haven't had any luck getting it to run well on my P2/400...
Re:I never consider trying it (Score:1)
Be (Score:4, Funny)
Shouldn't "Be" be called "HasBeen"?
Re:Be (Score:1, Offtopic)
they were never.
Re:Be (Score:5, Funny)
Re:Be (Score:1)
Why would I bother? (Score:2, Funny)
Re:Why would I bother? (Score:2, Insightful)
Egads (Score:5, Interesting)
Re:Egads (Score:1)
Re:Egads (Score:2)
Re:Egads (Score:3, Funny)
I think that would be:
The review is interesting, but it's been a while since I've seen such a glaring example of bad spelling and grammar in a live article on a high-traffic website dedicated to technical stuff.
But that's just par for the course on
Re:Egads (Score:1)
I think that should be:
Slashdot
But that's just me.
Re:Egads (Score:1)
I think that should be:
Slashdot.org
But that's just silly. =)
Re:Egads (Score:2)
Cheers.
Re:Egads (Score:5, Funny)
The review is interesting but it's been a while since I've seen such a glaring example of bad spelling and grammar actually make it as a live article in a high-traffic website dedicated to technical stuff.
Really? Maybe you should give this site [slashdot.org] a try.
Re:Egads (Score:2)
Re:Egads (Score:2)
ten minutes?
if this is a good review, I'd hate read a bad one (Score:2, Funny)
from the section entitled "BeOS in all it's glory":
I have an adsl connection here at home and this is where I ran into my first problem. There is a package for BeOS called PPPoE which lets you connect to any adsl provider that uses the PPPoE protocol. Of course, I installed it, configured it and dialed up my ISP. I get a connection, but only for about 3 seconds. Major pain in the ass! So I looked through the readme file, changed all the appropriate settings and still no cigar. "Well", says I, "It's time for the old tech support forum!" I rebooted into an OS with a decent PPPoE implementation, logged onto BeOSOnline and found an interesting thread in their forum suggesting I use BONE 7a. BONE stands for BeOS Networking Environment and is of fairly dubious legality. It was supposed to be part of the last release of BeOS, just before it got sold to palm but was supposedly never officially released. As Be was selling BeOS, some developer(s) on the project decided to leek BONE onto the net. Good old hacker disregard for authority! Finding BONE is not easy, but once I downloaded it I was supposedly ready to go. How wrong I was! I downloaded BONE to my windows partition as I already knew BeOS can mount, read and right to Fat32 partitions. I unpacked the Zip file, opened a terminal and ran the install script. Time to reboot. This is when the shit hit the proverbial fan. Instead of looking at my nice new desktop I was faced with the textual garble that is the kernel debugger!
Whew... so as long as you don't wanna use it for anything, BeOS is GLORIOUS!
Re:if this is a good review, I'd hate read a bad o (Score:3, Insightful)
This will get you a fast and smooth set-up which will allow you to browse the web, read e-mail, get work done, play mp3's and the choice of games are fair enough for recreation. My set-up (ASUS Laptop PII 366, 128MB, 4.2GB) boots in 9 seconds, starts apps in under 5 seconds, is fast (2x mpg, 2x mp3 and OpenGL (teapot) running at once - no loss), stable, cost me less than $200 (with s/w) - and BeOS found all the hardware.
Great for taking out and about, getting things done without fearing damage to the machine and easy for the kids to understand and play with.
But I agree on the remarks for the review - it did not do BeOS a favour.
PowerPC? (Score:1)
I was hoping to install BeOS onto my G4 so that I could tinker around with it, but now if I want it on my Mac I will need to use VirtualPC.
I say BRING BeOS BACK TO ITS ROOTS! PowerPC NOW! =)
Re:PowerPC? (Score:3, Informative)
Re:PowerPC? (Score:2)
But again, I couldn't DO anything with it. So away it went.
Nice Idea, but... (Score:2)
Re:PowerPC? (Score:2)
BeOS for PowerPC died when Apple stopped providing them with the ROM information, IIRC. I had BeOSDR8.3 (4?) running on my 8500/180MP awhile back. It ran very, very nicely in the dual CPU setup. The funny thing was the CPU meter application could actually be used to 'turn off' a CPU and you could turn off both CPU's, which of course crashed the machine. I think you could even run it on those Daystar machines that had four 200Mhz 604e's. Yikes.
Re:PowerPC? (Score:2)
Why stop there? Port it back to the AT&T Hobbit chip [bebox.nu]!!
This review was soooo bad (Score:2, Informative)
Re:This review was soooo bad (Score:2, Insightful)
I think the fact that he tried to burn two 650 meg ISO files on the same CD shows his level of technical savvy. I didnt even bother to read on. It would be like listening to a mentally challenged 3rd grader explain Shakespeare.
Re:This review was soooo bad (Score:2)
Wait a second.... (Score:4, Insightful)
Re:Wait a second.... (Score:2)
Heck, it took me about 10 seconds to explain to my non-technical grandfather the difference between writing files to a CD and a writing a file that contains a CD image to a CD.
Re:Wait a second.... (Score:2)
There were 2 filesystem images. One was aboot image (usually an image of a 2.88MB floppy) and the other was a BFS image (Install filesystem image). So he did need to burn both to a disc in order to boot it.
There are other things you can put on a CD-R other than a ISO image.
Re:Wait a second.... (Score:2)
fyi (Score:4, Insightful)
Re:fyi (Score:3, Informative)
Besides, I burned the image file to CD from PE and installed from it fine. Not documented officially, but it works quite well.
Paying any money for BeOS Pro is being ripped off. The bonuses it once gave are nullified by the negatives of its age. Max and Developer Edition have done a good job of extendending the life of the OS through third party applications, extensions, and replacements. It is a good hold over until a reimplementation is complete. I'll be the first to say that extending the closed-source release can only go so far, but it is a very good holdover until a complete solution comes along.
whose fault? (Score:2)
I was disapponted ~5 years ago when Be's team has rejected $18M acquisition deal from Apple.
Re:whose fault? (Score:2)
Re:whose fault? (Score:2)
I don't care about that someone will re-use ripped off good parts. I care that the good code would not dye like it is dying now in Palm.
And I am not a stock holder. I just care that BeOS had some good ideas that time, but as a whole OS it was obvious (even then) that it won't survive (it was a mix of good and bad ideas withut any marketing and any support).
That time I didn't see upcoming in 3 (?) years MacOSX and I was unhappy to use that crap, called MacOS. MkLinux also looked like a very extreme experiment that time (especially comparing to Linux/x86). So, I had a hope that Apple will move to BeOS and bring a whole bunch of commercial software vendors with itself.
It didn't happen. Apple moved to MacOSX with all commercial vendrs. BeOS now is really dead (and who cares now?). MacOSX will buy 2 or 3 years to Apple to forget about OS problems. Until Linux/PPC will finally knock the Apple's door after successfully booming on x86 PCs.
Re: (Score:2)
What the hell is the status of BeOS? (Score:4, Interesting)
What gives. Are these rouge distros or what?
Are they legal? Is there any reason to belive that Palm won't pull the plug on any variants out there at any given time?
I'm sincerly trying to understand the situation. Links are appricated.
-Peter
Re:What the hell is the status of BeOS? (Score:5, Informative)
For open-source replacements of BeOS check out the following:
OpenBeOS [openbeos.org]
BlueEyed OS [blueeyedos.com]
also look at the following:
beunited [beunited.org]
yellowTab's Zeta [yellowtab.com]
The guy writing the review is a horrible representative of BeOS users, i think. it's my main OS at home, and I have had little teouble with it, ever (the only time i went into Kernel Debug land was when I managed to crash snes9x with a corrupted ROM).
Re:What the hell is the status of BeOS? (Score:2, Funny)
Not Free as in Beer, nor Free as in Speech.
But Free as in 'not worth Jack-Shit'
Re:What the hell is the status of BeOS? (Score:1)
Re:What the hell is the status of BeOS? (Score:5, Informative)
As I understand it, we have several different variants:
And there you go.
Note that I'm not really a BeOS enthusiast, so I may be wrong about some of these. However, that's what it looks like to me.
BlueEyedOS (B.E.OS, formerly BlueOS) (Score:2)
B.E.OS does NOT implement BeOS binary compatibility. I see this as a significant flaw. If you are going to use the Linux kernel to recreate BeOS (A completely rational decision in my opinion - like anything else I'd rather see it implemented on top of mach but I'll settle for anything stable with good driver support) then you should really be planning to implement BeOS binaries in the linux kernel; if not immediately, then somewhere down the road. Not supporting BeOS binaries will ultimately hurt you. I wouldn't make it a high priority or anything, but I do think it's worth doing.
Building a new BeOS on top of the Linux kernel DOES make more sense than any other possible option at the moment, because you get instant driver support for a vast range of hardware. A system of module management should be considered as a means for controlling hardware more closely. (Think being able to unload a module and load it with new arguments, runtime configuration is important. People who build anything not absolutely necessarily internal to their kernel directly into their kernel are missing out on a really fantastic feature. But I digress.)
The B.E.OS unfortunately has a restrictive license which denies commercial use amongst other things, they deliberately want to keep central control. I disapprove (I would prefer even GPL to that) but the fact that they're doing it all is a possible boon, and at least they're using a linux kernel so it's not like there's going to be spooky magic under the hood or anything.
Re:What the hell is the status of BeOS? (Score:3, Informative)
Wrong, it requires that you are smart enough to burn a boot image and a disk image to a cd to be able to do a full install.
The BeOS Developer Edition above is apparently a release of BeOS Max Edition. This is basically BeOS Personal Edition with patches applied, new drivers and various open-source contributions. It's maintained by volunteers.
No BeOS Developer Edition has been out for a long time (basically since palm bought be and be stopped hosting the downloads for pe and making updates), Max Edition is basically the same thing (the free version of BePE plus some updates) done by another group.
The BE File System (Score:5, Interesting)
All said and done, I think the developers of BeOS did a really great job. I recent got the chance to go over the Be File System (BeFS) for class and was amazed by what they did in a short amount of time (less than a year). If you want to look at a short presentation on the file system, you can grab it (in ppt) from here [cmu.edu].
New MS filesystem to be Be-like... (Score:2)
Another Distro (Score:3, Informative)
http://prdownloads.sourceforge.net/crux/BeOS5PEMa
Home page
http://crux.sourceforge.net/nuke/index.php [sourceforge.net]
Help me out, please (Score:2, Interesting)
I so want to like this OS, but when I installed it, it didn't strike me as more usable, faster, or anything.
A brief list of what its users really like about it as opposed to the billions of desktops (Windows, all the linux ones, OSX) might be beneficial to more than just me. I guess what I am asking is, where should I be looking for the greatness, or even novelty.
Re:Help me out, please (Score:5, Informative)
Boot-up speed. Turn PC on, wait for HDs to spin up, tap toes for three seconds, start doing things.
SoundPlay. World's best mp3 player bar none. Shareware yes, but it really IS worth the money for once.
Ease of use. I have never come across a network setup that was as easy as BeOS's. Enter hostname, enter domain name, check DHCP box, click apply, start the browser.
Didn't like:
Hardware compatability. If you can't get drivers (check the Hardware Matrix [frizbe.net] on here) for your hardware change your hardware or don't bother.
Lack of apps. My needs are basic so it did all I needed it to, but not all I wanted it to.
Still kicks arse. And I still use it a couple of times a week. Give it a spin, see how you like it. If OpenBeOS gets the Open Source fanatics behind it it will rule.
-Mark
Re:Help me out, please (Score:2)
Given that BeOS code ran fast on (relatively) slow hardware, it stands to reason that it would run like a bat out of hell on modern pumped-up hardware. (Given proper drivers, of course... and there's the rub)
Outdated (Score:2)
I mean -> Could this B OS date out any more.
Or Maybe, I could B a little Kornier!
PERFECT (Score:4, Interesting)
I love Linux, love Open Source and all it stands for, but I'm sorry to say, it will never be able to deliver an elegant desktop sulution.
As far as I'm concerned BeOS, could have been the most perfect home-PC solution. Regardless of whether it could ever find mainstream acceptance it not the point.
Sure, no driver support, and nothing but half-assed apps to play around with, but still. The OS achieves a kind of balance, "perfection" if you will...
Any group or company looking to overhaul Linux for _actual_ desktop use should take a very close look at BeOS. The way the OS is structured, the way deviced are handled, the simplicity and flexibility of the GUI, the way the shell coexists with the GUI.
I don't want "full" UNIX, just the stuff that matters to me: A quick, good and consistent user interface, modern applications/drivers/utilities/, a clean directory structure, a refined, legacy-free configuration options to mess around with... and who knows? maybe even some ports of Linux apps
Re:PERFECT (Score:3, Interesting)
Comment removed (Score:5, Insightful)
ACs? elitist Linux users or just trolling pussies? (Score:4, Insightful)
Why are all the AC's ragging on BeOS? Funny, I seem to recall a little software project called Linux that happened to be in a similar situation as Beos.
Yup. No hardware support. Little software. Proto usefulness, if that.
Now what do we have? Linux is THE open source solution. It has come a long way.
How much of that progress are all you ACs responsible for? Not much, I'm sure. Just run your perl scripts and feel superior to windows 98 users. Whoopie.
OpenBeos and all its ilk are right where Linux was several years ago. The difference is that the people working and waiting on OpenBeos want it more than people want YALD (yet another Linux Distro). Another difference is that OBeos can be designed from the ground up to work better with today's hardware, can avoid the dead ends of the past, and have lots of good examples of UI, software, and ways of doing things that can be improved and incorporated.
My suggestion to AC is that you all shut your pie holes and *encourage* OSS of any sort, otherwise you may find developers for your favorite OS (OF CHOICE) going off and doing web pages for Microsoft.
No one needs or wants some faceless pussy ranting about how their labor of love is irrevelent.
Mod away, kids.
Re:And in one sentence, he described BeOS communit (Score:3, Interesting)
Re:And in one sentence, he described BeOS communit (Score:3, Insightful)
Re:And in one sentence, he described BeOS communit (Score:2)
And what exactly are you expecting? Do you think someone's going to write an AutoCAD workalike and release it as open source, all for an OS with something like 5 total users worldwide? Fat chance. Something like that takes time, expertise and manpower.
Just blame it on the other guy (Score:2)
Re:And in one sentence, he described BeOS communit (Score:2)
Re:And in one sentence, he described BeOS communit (Score:5, Informative)
How about decent file typing? That's one thing BeOS did well, using MIME as the native file typing mechanism. MacOS had pretty good file types, but Apple seems to be discouraging it's use in favor of the lowest common denominator: file extensions. Which are frankly, crap.
Linux is probably at the bottom of the heap here. Both Gnome and KDE are starting to maintain their own databases of this stuff, which is pointless because this should be a common service OS-wide. An application should be able to ask the OS which application should be called to handle text/html for example. But there isn't any standard way to do that on Linux. As a result, different applications do different things when I click on a link. I want a Konq window to open, but there isn't any way for me to tell Evolution that. It insists on opening a Mozilla window.
I'm sure eventually this will get solved on Linux, but BeOS was handling this problem quite well five years ago. It isn't rocket science, in fact it's pretty simple.
Another example is file metadata. BeOS allowed you to add arbitrary name/value attributes to files. What's more, you could have the filesystem index them to allow you to do quick searches on them. Plus the Tracker allowed you to specify what attributes you wanted to have displayed in folder windows. You didn't have to look at the file name and size if you didn't want to. You could view only custom metadata.
This works great for audio files. The developers standarized on a set of attributes which all the major MP3 applications use. So all of my MP3 (well, Ogg actually) files have the artist, album, track, etc saved as metadata. The Tracker can be told to only display those attributes, if you want. Plus the OS can search on them. I've got a ripper thats adds the attributes when I rip a CD. I've got a file viewer, the Tracker, which lets me sift thru my collection looking at the relevant metadata. And I've got a player which lets me add file, folders, and arbitrary metadata queries to playlists.
Unfortunately, having my jukebox based on a dead OS is getting to be a drag for other reasons. So, I'll probably try to move the whole thing to Linux, but it'll be painful. I'll have to install my own database to handle the metadata. There's no standard schema so the few MP3 apps which do use databases won't interoperate. Not to mention that having the actual files and metadata completely disconnected is an extremely fragile solution. If you move a file using the normal techniques, then the metadata is out of sync and you have to fix it somehow. So I do what? Write my own interface for providing simple file manipulations so that I can keep the metadata in sync? That's not really practical either. In the end, I'll probably spend a lot of time implementing a solution that will work half as well.
Not that BeOS was perfect, far from it. Shall I discuss the pain of porting network software to an OS where sockets are not file descriptors? But it did have some really nice features which I have yet to find in any other OS.
Re:And in one sentence, he described BeOS communit (Score:2)
Re:And in one sentence, he described BeOS communit (Score:2)
Unfortunately we live in an imperfect world.
Re:And in one sentence, he described BeOS communit (Score:2)
But what about when I want to search the metadata in all of my songs? I've got something like 10GB of Ogg's. A majority of my music collection. Should the player search every file every time I do a query? No, that's ridiculous of course. Should I have the player scan every single song when it starts up and cache the infomation? Maybe if you don't mind reaaaly slow startup times. No, the place to keep that much information if you want to search it is in a database. And that's what BeOS did, in a nice simple standardized API. Oh, and did I mention that the queries can be live under BeOS? So if files are added or deleted which match an active query my application gets informed? There isn't really any way to replicate that with just ID3 tags without either polling (expensive) or kernel mods (which have their own development headaches.)
Re:And in one sentence, he described BeOS communit (Score:2)
Re:And in one sentence, he described BeOS communit (Score:2)
But without the indexes, the attributes aren't useful for search-oriented actions. In my case, I really abuse the ability to search in my jukebox software. But since both MP3 and Ogg Vorbis include ways to store metadata in the stream itself, XFS doesn't add much benefit.
Re:And in one sentence, he described BeOS communit (Score:3, Interesting)
Why isn't there a program called "start" or "open" that takes a url and does whatever would happen if the user double-clicked on it? Then all the desktops could call this program. And the program could be replaced (there is no need even to agree on the implementation, both KDE and Gnome could put out their own "start" program and the user decides).
Even Windows has a "start" program. Why does the supposedly CLI-based Linux NOT have one?
Re:And in one sentence, he described BeOS communit (Score:2)
Under BeOS it was a library call, but a lot of things in *nix land are small programs instead of libraries. I wonder if anybody has already hacked something similar up?
Re:And in one sentence, he described BeOS communit (Score:2)
metadata belongs in the filesystem (Score:2, Interesting)
This is the direction that ReiserFS [reiserfs.net] is moving toward [reiserfs.net].
However, Linux's inherent view of files (ie. everything is a file) is not necessarily wrong. This allows many very easy solutions to problems. It makes it easy for applications which want to use a device; they simply read or write to a file. It also makes it easy to monitor your system; just read proc files with a text parser.
So in conclusion, Linux's current view of files is not incompatible with metadata, and there are many advantages to viewing files in the way that Linux does.
Tony
Re:metadata belongs in the filesystem (Score:3, Interesting)
Sure, but having additional metadata does not prevent things from working the way they do under Linux. In fact, for most things, BeOS looked just like any other Posix system. Devices were files, and all the standard Posix read/write calls were there. There were downsides, of course. You could accidentally trash the metadata if you weren't careful. The 'cp' command, for example, didn't copy the metadata (which I consider to be a bug, but oh well). And of course if you used FTP or something to copy files around it got lost. It wasn't hopeless, of course. If you copied files in the tracker, it did the right thing. And all the zip/unzip binaries for BeOS maintained the attributes so you could safely move the files between systems.
So the two can co-exist. In fact, there is a filesystem driver for BFS in the kernel now. Last I looked, but was read-only. But it's certainly possible for it to become read-write and for the whole index/attribute API to become available under Linux. You would have the same risks as under BeOS (tar,cp,scp,etc. would lose the metadata), but even that could be fixed. 'cp' can already be told to preserve the metadata it knows about. 'tar' is a lost cause because you'd probably have to try and change the file format which wouldn't go over very well.
I'll read the white paper on reiserfs you linked. Maybe it'll end up providing some of the stuff I want.
Re:And in one sentence, he described BeOS communit (Score:2)
Re:And in one sentence, he described BeOS communit (Score:2)
Re:And in one sentence, he described BeOS communit (Score:2, Interesting)
Re:And in one sentence, he described BeOS communit (Score:3, Insightful)
Then I realize that I can't get a decent speedy browser, that I can't work on my resume, that I can't play the games I want, that I can't do my bills online either from lack of Java to lack of a quicken type app.
My partition will rott away, I fear. BeOS is the biggest heartache for me as a computer user and professional. So much potential, so little of anything else.
Re:And in one sentence, he described BeOS communit (Score:2)
Re:And in one sentence, he described BeOS communit (Score:2)
Re:And in one sentence, he described BeOS communit (Score:2)
But that's besides the point. The old line about "BeOS is dead because is has no users and no apps" is about as valid as "Linux will never make it to the mainstream"
Re:And in one sentence, he described BeOS communit (Score:4, Interesting)
i was quite amazed by the amount of opensource/community developed drivers for it(obviously lot of 'em derived from linux driver sources), and the whole community actually being there in general.
Re:And in one sentence, he described BeOS communit (Score:5, Insightful)
Well, right after I installed it was treated to booting into an OS that thought I was in France. Fine, not a big deal, but it would have been nice if the documentation (all in English) had mentioned this and maybe even described the process by which you fix it the language settings.
Then I got to experience the full glee of BeOS resending 16 email messages I had already sent from its mail program... about two years ago! I emailed the developers about this and got no response.
This is usually where the Be apologists will insert some vague praise of it's microkernel architecture. Yeah, it's great I can drag and drop a driver into the system folder and have it start working right then, but so what if it's totally impractical to actually *use.*
So I blew away the partition and said, "Goodbye BeOS, it had been fun." When an OS is new, you can forgive it for having no application support and no hardware drivers. Now, 2003, we're nearing 8 years with BeOS on the PC and almost all of the drivers we have today we had back then (exception: a non-accellerated nvidia driver). Application support continues to hover around the few commercial apps it had three years ago (though I believe Gobe has dropped BeOS support for Productive). When I last ran the OS, most of the software for it suffered from the same Windows delusion that every schmuck who downloads a shareware program is willing to chip in $10 for it. Consequently, actually achieving productivity with BeOS was difficult because you'd wind up paying hundreds in piss ant shareware fees to unlock the full features of whatever it was you wanted to use (see BeXL, all of the good code editors, SoundPlay).
So BeOS lost a fan in me. The only chance for redemption will be when OpenBeOS starts making releases, but even then it will be a long shot. If you doubt me, check my previous posts and you'll see, I used to be one of their supporters around here, but I give up. OS X certainly kicks BeOS in the nads, thanks in no small part to NEXTSTEP. I haven't used WinXP but wouldn't be surprised if much of what made BeOS advanced almost a decade ago had finally been integrated into Windows.
--
Daniel
Re:And in one sentence, he described BeOS communit (Score:2)
What hurts BeOS is the lack of third party support. For a 'multimedia os' it had/has crappy format/codec support. Applications were sparse. Linux had these same setbacks once upon a time, but the nature of the platform lent itself well to a grass roots movement of software developers, and BeOS did not. They offered decent tools, but the proprietary, closed source core really didn't appeal all that much to developers that already could do stuff with Linux. Sure BeOS was a more 'all-in-one' package with a better graphics system, but the business behind it killed the technology.
Re:And in one sentence, he described BeOS communit (Score:4, Funny)
No shit. As an OS/2 user, the BeOS fans make me look like the popular kid in high school!
Re:And in one sentence, he described BeOS communit (Score:4, Interesting)
But OS X is fucking slow. So slow, in fact, that I've stuck with Linux and never looked back on fifteen years of Mac usage. I installed BeOS on my old 300Mhz Dell Latitude, which fortunately has one of the rare combinations of hardware that BeOS supports. It is blazingly fast. It blows Win2k right out of the water, and is very competitive with Linux. In fact, the only reason it isn't necessarily faster outright than Linux is that I'm using WindowMaker and not bloated crap like KDE or GNOME. Too bad it isn't actually useful enough to replace Linux.
OS X has been a huge disappointment for me. The lack of customization is painful. The speed is horrendous. The Unix compatability is so broken as to be virtually useless. I'd take it over XP any day, but I'm sick of hearing about how great Apple is for bringing Unix to "the masses". It's markedly inferior to BeOS and IRIX from almost any perspective except application availability. I find little to admire in any user interface released since, say, 1993/4, and of course consumer OSes are just now catching up to features that enterprise OSes had long before then, like not crashing every few hours.
I compromise with Linux and IRIX. I may have to recompile the kernel just to link with my Zaurus; I have to jump through hoops to handle Word documents- I find using Crossover less painful than using StarOFfice. And the SGI, of course, can't even do most of this. But I can always be certain that, once I've spent two weeks setting it up, my computer works the way I want it to, not the way the trained chimps over at Apple and Microsoft dictate, and that it won't creak to a halt when I try to edit a file because 90% of the CPU is stuck rendering antialiased menu bars.
Re:And in one sentence, he described BeOS communit (Score:2)
Actually, I'm a professional programmer, who works entirely on Unix, and administers several Linux servers at work (wholly apart from my personal tinkering). I ditched OS X after Apple broke NIS compatability in 10.2, which pretty much made it useless for our environment. That's in addition to their already horrid support for NFS. And the impossibility of configuring everything on the command line.
As for speed, 10.2 is still too slow. This is just the same old excuse that Microsoft makes - "it doesn't suck as much as it used to." I have no desire to continue waiting for Apple to get it right; my boss wants things done now.
Re:And in one sentence, he described BeOS communit (Score:1)
Re:Nah (Score:1)
Do I make sense?
Re:WHY? (Score:2)
You actually make your own food!?
Come on man, the folks who tinker either do it because they like to, or they have to.
Re:Without apps it's useless. (Score:2)
Wrong, there is Gobe Productive which is on par with staroffice if not better. Really the only thing BeOS lacks is a decent photoshop type program. There may be a version of gimp for beos (not sure), but gimp isn't really a substitute for photoshop except for people who haven't used the former.