If you bothered to pay attention to the field of BeOS developement.. you might retract a few of those statements. 1) R5 can be downloaded and installed in either Windows or Linux, or you can buy an actual copy of it, and get install media, and a handbook (for the same cost as many linux distros). 2) It's trivial to install the downloaded version onto a bare drive, once it's up and running. 3) it's not running under windows or linux. It stores an FS image in there, and then kicks that the other os's ass out of memory when it runs. It just does a softboot of the machine. Also, there is significant developement in the networking section, along with the opengl section. (both of which make BeIA a better product). But, I guess we can't fault you for TRYING to sound like you know what you are talking about.:: linux - 'cause a 14 year old kids code is good enough for me::
I do everything on my BeOS box. Code, play, watch movies, IRC, burn cd's, all sorts of things. I make movies with my tv card, surf the web, AIM, the normal things. What ever you do on the other OS's, I do.
I let my OS do the "configure and work" part. That's what it should do. Were advanced enough in the world that my computer can understand it's own hardware and load the correct device driver. However, you can press the space bar on boot, and go into vesa mode, then download a GeForce driver off bebits.com. (yes, it works, no, there is no opengl.). Anyways, if you read the html files that are installed with BeOS, you would have found the software sites easily enough. BeOS has a community just like the other OS's, and it's a pretty well layed out community.
Hardly. I don't know if i'm an extreme case or not, but the only OS i've run for the past year has been BeOS. Sure, i've got a BSD box around, things like that, but I only use BeOS for my work.
First off, i'm not sure where you got the 5 nic cards supported number. There are tons of nics supported. http://www.be.com has a good list of hardware supported. There is a perfectly working X server for BeOS. Why would you want to compile an X based app for BeOS, and use a 20 year old (or older) windowing system? Why defeat the purpose of BeOS? You could throw in a compatibility layer, but that would be not really worth the development time, because of the very nature of compatibility layers. I don't recall normal X programs compiling with out a glitch (or minor tweaks) on Windows. The BeOS port of Mozilla is almost up to date, and I have a working binary on my system. BeOS still has many hopes. It has lost nothing, there is just tons more to gain. Honestly, masking your flaim bait as an "I support Be, but I got screwed by them" post is pretty bad.
Or, that they don't have 400,000 people wasting efforts hacking on the same code base, to introduce 200,00 variations on the same optimized window blitting loop. Personaly, i've never found anything BUT quality in BeOS. I don't crash, SMP is a dream, and applications launch in a mere second, even under a machine with a huge load. Honestly, your comments were nothing but flame bait, and pretty bad at that. Most code (if you have experience with the coding style and code base) is self documenting.
--- MouseDown ---
Hardly. I've been following the bug database for a while now, and there are tons of posts (read that as good) about the new networking stacka, and things that developers would like to be implemented. Also, the lack of bug reports does not mean a thing. I'd say it's a pretty good sign that with the current release of software that the OS is fairly stable, from a developers point of view.
".. or ext2+tree patch uses. HPFS no doubt uses it to.."
Note the patch there. BeOS comes with it default, no hacking, tweaking, or fighting bad installs to get it setup and working. I don't know about you, but I like *nix, but I sure as hell hate fighting installs for 3 days, trying to get my new computer up and running with it's shiney new OS.
class BeOS : public CoolOS....
I don't know, but when I can play 40 mp3's at 128k on my dual p2 350 box (~600mhz with all the messaging overhead and what not) and still have my OS remain fully responsive, that seems to speak leaps and bounds about the core technology. Sure, you might be able to play a bunch of mp3's at once with ALSA, but that will bring the machine to it's knees. And yes, I venture outside the BeOS world. I run a FreeBSD box and a LinuxPPC box.
It is also very easy to mass edit the meta data for mp3's. There are programs (free) for BeOS that exports the id3 information right into the attributes (fs meta data), where it can be queried from inside any program, or the Tracker (file manager). Personaly, I find that it makes running an mp3 stream incredibly easy.
It ran exceptionaly well on my FreeBSD 4.01 box. My machine was a dual p2 350, 256mb ram, and it handled like a dream, task switching, redrawing, all the good stuff (tm). I'd recommend it to anybody, and the ports tree makes it a breeze. cd/usr/ports/x11/kde2; make; make install; That's all it took for me, and a few hours later, I had kde2.
It'd be a massive undertaking to provide a link to all the things listed in each story (eg cvs, efm, kde), but for anybody in the computer geek community (alt. os), then they almost all make sense. But, your travels will take you to new places, depending on what your interests are. Read!
Actually, my 200mhz PPC box (604e) runs exceedingly fast in LinuxPPC. I was able to use the box to serve 150,000 static page hits in a couple days (bandwidth limited, not processor). I ran remote X, so I don't know how good the local X server is, but it ran pleasently well on my BeOS box.
::BeOS::
If you bothered to pay attention to the field of BeOS developement.. you might retract a few of those statements. 1) R5 can be downloaded and installed in either Windows or Linux, or you can buy an actual copy of it, and get install media, and a handbook (for the same cost as many linux distros). 2) It's trivial to install the downloaded version onto a bare drive, once it's up and running. 3) it's not running under windows or linux. It stores an FS image in there, and then kicks that the other os's ass out of memory when it runs. It just does a softboot of the machine. Also, there is significant developement in the networking section, along with the opengl section. (both of which make BeIA a better product). But, I guess we can't fault you for TRYING to sound like you know what you are talking about. :: linux - 'cause a 14 year old kids code is good enough for me ::
I do everything on my BeOS box. Code, play, watch movies, IRC, burn cd's, all sorts of things. I make movies with my tv card, surf the web, AIM, the normal things. What ever you do on the other OS's, I do.
I let my OS do the "configure and work" part. That's what it should do. Were advanced enough in the world that my computer can understand it's own hardware and load the correct device driver. However, you can press the space bar on boot, and go into vesa mode, then download a GeForce driver off bebits.com. (yes, it works, no, there is no opengl.). Anyways, if you read the html files that are installed with BeOS, you would have found the software sites easily enough. BeOS has a community just like the other OS's, and it's a pretty well layed out community.
Hardly. I don't know if i'm an extreme case or not, but the only OS i've run for the past year has been BeOS. Sure, i've got a BSD box around, things like that, but I only use BeOS for my work.
First off, i'm not sure where you got the 5 nic cards supported number. There are tons of nics supported. http://www.be.com has a good list of hardware supported. There is a perfectly working X server for BeOS. Why would you want to compile an X based app for BeOS, and use a 20 year old (or older) windowing system? Why defeat the purpose of BeOS? You could throw in a compatibility layer, but that would be not really worth the development time, because of the very nature of compatibility layers. I don't recall normal X programs compiling with out a glitch (or minor tweaks) on Windows. The BeOS port of Mozilla is almost up to date, and I have a working binary on my system. BeOS still has many hopes. It has lost nothing, there is just tons more to gain. Honestly, masking your flaim bait as an "I support Be, but I got screwed by them" post is pretty bad.
Or, that they don't have 400,000 people wasting efforts hacking on the same code base, to introduce 200,00 variations on the same optimized window blitting loop. Personaly, i've never found anything BUT quality in BeOS. I don't crash, SMP is a dream, and applications launch in a mere second, even under a machine with a huge load. Honestly, your comments were nothing but flame bait, and pretty bad at that. Most code (if you have experience with the coding style and code base) is self documenting. --- MouseDown ---
Hardly. I've been following the bug database for a while now, and there are tons of posts (read that as good) about the new networking stacka, and things that developers would like to be implemented. Also, the lack of bug reports does not mean a thing. I'd say it's a pretty good sign that with the current release of software that the OS is fairly stable, from a developers point of view.
".. or ext2+tree patch uses. HPFS no doubt uses it to.." Note the patch there. BeOS comes with it default, no hacking, tweaking, or fighting bad installs to get it setup and working. I don't know about you, but I like *nix, but I sure as hell hate fighting installs for 3 days, trying to get my new computer up and running with it's shiney new OS. class BeOS : public CoolOS ....
I don't know, but when I can play 40 mp3's at 128k on my dual p2 350 box (~600mhz with all the messaging overhead and what not) and still have my OS remain fully responsive, that seems to speak leaps and bounds about the core technology. Sure, you might be able to play a bunch of mp3's at once with ALSA, but that will bring the machine to it's knees. And yes, I venture outside the BeOS world. I run a FreeBSD box and a LinuxPPC box. It is also very easy to mass edit the meta data for mp3's. There are programs (free) for BeOS that exports the id3 information right into the attributes (fs meta data), where it can be queried from inside any program, or the Tracker (file manager). Personaly, I find that it makes running an mp3 stream incredibly easy.
It ran exceptionaly well on my FreeBSD 4.01 box. My machine was a dual p2 350, 256mb ram, and it handled like a dream, task switching, redrawing, all the good stuff (tm). I'd recommend it to anybody, and the ports tree makes it a breeze. cd /usr/ports/x11/kde2; make; make install; That's all it took for me, and a few hours later, I had kde2.
It'd be a massive undertaking to provide a link to all the things listed in each story (eg cvs, efm, kde), but for anybody in the computer geek community (alt. os), then they almost all make sense. But, your travels will take you to new places, depending on what your interests are. Read!
Actually, my 200mhz PPC box (604e) runs exceedingly fast in LinuxPPC. I was able to use the box to serve 150,000 static page hits in a couple days (bandwidth limited, not processor). I ran remote X, so I don't know how good the local X server is, but it ran pleasently well on my BeOS box.
::BeOS::