Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Linux Software

What Would Happen To Linux If BeOS Were GPL'd? 298

j2demelo writes: "What would happen to Linux if BeOS were to be released under the GPL? How much competition, if any, would this bring upon Linux? I for one would love to see it happen. It would mean another low-cost alternative to Windows on the desktop, allowing computer manufacturers to reduce prices even more. We know Linux isn't currently ready for mainstream desktop use. Could the open sourcing of BeOS give it the kick-in-the-butt it needs?" Before you all start the advocacy wars, I'd like to point out that if BeOS was converted to an Open Source License, it would not mean the end of either OS by a long shot. Competition in markets usually means an improvement of the products in that market, that would mean that both Be and Linux would have to improve. What improvements would both OSes make and how would this affect the Open Source Operating Systems market?
This discussion has been archived. No new comments can be posted.

What Would Happen To Linux If BeOS Were GPL'd?

Comments Filter:
  • Fucking bullshit and a very lame try bastard. Put any page's name in front of @ and it will show up. Son of a whore.
  • Most likely, the good points of the BeOS architecture would be incorporated into Linux... and some things in Linux would go into BeOS (do to released licensing pressure). This would be a very good thing for linux... but mostly on a usability side.

    Unfortunately, a lot of the cool things that BeOS can do are because of the overall architecture. It is highly unlikely that the fundemental unix like architecture of linux will change. Instead, we will have to wait for a preemptible, pageable kernel to get developed. Then wait for filesystems to get far enough along to support "interesting" things.

    Linux's main problem (which is also the source of much success... :) is that it doesn't make radical enough changes. Distributions are all so alike, that it's sickening. It would be much more interesting if they tried a fundementally different architecture. Perhaps apple's work could be just another "distro" of Linux (I know they aren't based on linux. The point being that they actually tried a different naming heirarchy... wow. ;)

    Anyways, one could claim that the Linux community is very good at cloning prior art, but not very receptive to radical developments of it's own.

    -Chris
  • Wow, it must be a day for alternative operating systems! First, Inferno, then Amiga, and now BeOS? What next?!?1

  • by wyrmBait ( 19085 ) on Friday December 15, 2000 @07:04PM (#555082) Homepage
    I question the reasoning in Cliff's comment after the story. He's citing the common idea that competition in a free market results directly in an improvement in the competing products, and I'm not sure this applies to the OS community in such a direct way. After all, how much pressure to improve itself has Linux felt from *BSD? What about Darwin or the Hurd? Being newer than most to the community, I put this as a question to those of you who would know it firsthand.
  • I would love to see BeOS gpl'd
    I have used it before and love it, the only problem is that Be has a relativley small team of developers and they don't have enough driver support for the things on my existing computer, I would have to get another one to run it right.
    I don't really see that it would compete with Linux in all that big of a way.

    I remember an interveiw with Linus on a radio station here in seattle (99.9 kisw for those of you reading from here) where he said that he had created it because nothing else really suited the way he wanted to use a computer and he wasn't really trying to compete with windows he just wanted their to be more choices the same way that "Mac" is a choice.

    Is this just a "what if?" question or has something been hinted at from Be?
  • by timothy ( 36799 ) on Friday December 15, 2000 @07:06PM (#555085) Journal
    another data point arguing for the importance of platform-neutral file formats and programs which produce them by default.

    To argue for that, let me argue for a second against the opposite situation;)

    Microsoft Word, though I'm not a fan, is an adequate program for manipulating strings of words. It has find-and-replace (my favorite missing feature in pine;) ), a spelling checker, etc. Without getting into my particular complaints, I concede that many people like MS Word. But MS Word *could* be a morally / aesthetically acceptable program to me for all its failings, but it's not now. Why? Because its default file format is obfuscated and proprietary, and requires someone else to have either their own copy of Word or a special limited-purpose reader, and is difficult on anything but a Mac or Windows-running PC.

    That's lunacy. Analogies fail. It's as if ... how would you like medical charts that required every doctor who wanted to look at them and even had your permission couldn't do so without having the same brand of printer that created them?

    At any rate, I'd like to see an open sourced BeOS (not that it seems to be in the cards) if it would poke people with the idea that HTML, SGML, RTF, plain text and other such *un*obfuscated formats are the way to go. Documents in (even half-decent) HTML I think will be more likely legible than Word version X in 20, 30, 100 years.

    Anyhow, the continuing rant ...

    timothy
  • by j.e.hahn ( 1014 ) on Friday December 15, 2000 @07:11PM (#555089)

    Quite a bit actually. BSD used to tout the vast superioirty of their TCP stack over Linux. That's less true today than it once was. BSD folks love (loved?) to tout the superiority of ipf over ipfwadm and ipchains (rightly so), but I think iptables (new for 2.4) has it pretty well matched.

    You'd need to read the linux-kernel mailing list archives for a while to realize there's actually a fair amount of synergy going on there, and the core developers do occassionally discuss.

    A while back, as another example, BSD analyzed Linux's VM system (and criticized as well as complimented it where necessary). A lot of those criticisms were taken to heart.

    As for Hurd... I don't know enough about Hurd to tell you whether it even contributes to the community with new, interesting ideas. And darwin is just FreeBSD with apple sauce.

  • by VAXGeek ( 3443 ) on Friday December 15, 2000 @07:11PM (#555090) Homepage
    ok, i'm probably going to get moderated down for saying this, but... probably nothing. the open sourcing of other operating systems, darwin from the MacOS and plan9 haven't done anything to linux. the open sourcing of beos (which is _HIGHLY_ unlikely) would have NO effect on linux, aside from a few kernel patches if the license would permit (which it wouldn't). so, rob, can't you find a better way to generate more traffic? here's a few ideas for you to help add a few more $ to the money bin (like from duck tales haha)

    Ask Slashdot: which is better, freebsd or linux?
    Ask Slashdot: should i replace my NT server with linux?
    Ask Slashdot: is mysql ready for the enterprise?

    all of these discussions are just ploys to generate banner ad revenue. but, i KNOW that there have to be lots of decent stories out there getting rejected, just look at k5, it's pretty decent.
    ------------
    a funny comment: 1 karma
    an insightful comment: 1 karma
    a good old-fashioned flame: priceless
  • by cluening ( 6626 ) on Friday December 15, 2000 @07:13PM (#555092) Homepage
    I actually think BeOS is the coolest desktop OS I have ever used. Just to keep the record straight, I normally use and develop for Linux, and have played with everything Windows, Linux, OpenStep, Be, MacOS, and a couple others, but by no means every single OS out there. But in the end in my mind BeOS wins. It is really snappy, has a greay interface (a little rough around the edges every once and a while, but really cool nonetheless), and keeps things simple on the surface. But if you want, there is also that command line that lets you run all kinds of Unixy stuff a little deeper in the OS. So, basically you have a Unix-like OS (definitely not a flavor of Unix, but modeled after the same idea) that has a wonderful, very fast interface built in - Like OSX, only a lot better! The whole graphical nature of the OS is built in (unlike X on Unixes), meaning things like driver updates, time changes, etc (the normal maintenence stuff) is easy, but behind it is the power of a Unix like system. This is probably about the tenth time I have said it, but I think that is a really great design.

    So, why do I use Linux more that Be, even though I like it so much? One real reason - I know more about Linux, have more apps that I use a lot under Linux, and don't have a big enough hard drive to give both a respectable amount of space. So, in the future I may easily swith to Be full time (as long as they don't drop the OS for BeIA) and make use of the X server that has been ported to it for any X stuff I need. But I think Be really has a great product on their hands.
  • by Dungeon Dweller ( 134014 ) on Friday December 15, 2000 @07:15PM (#555098)
    At the risk of being attacked brutally...

    I think that more people cling to the GPL because of linux than the other way around. I don't see a lot of people screaming towards the HURD project, which is a pretty good concept.

    I think that more people attack the BSD license because of what certain advocates say, rather than the licenses actual content. I am a BSD user. Anybody who has seen my car knows this.

    I think that a lot of BeOS would get incorporated into Linux, but it would take time, especially considering the parts that are fundamentally incompatible, but that is beyond the scope of this discussion.

    And BeOS isn't going GPL. Why don't we talk about if Solaris or SysV or HURD, oh wait, that is GPL, go GPL instead.

    What would happen if every linux project switched to the BSD license? Would everyone leave linux and switch to BSD?

    (BTW, I also have a Linux box that I use the hell out of)

  • You make a pretty big assumption here... that being that BeOS itself is not a "rock solid OS" and porting it's GUI to linux would help.

    This really isnt the case. BeOS itself is just as stable as Linux. Nearly everything runs as a server on top of the kernel, and if it crashes, it just restarts that server.

    As far as porting the Be GUI to linux, it also couldnt happen. It would require basically recreating the Be API from scratch, and rewriting almost all of the linux kernel due to different ways of handling scheduling and threading.

    In fact, large chunks of the Be GUI are already opensourced at opentracker.org, but porting it to linux would be VERY difficult.

    With all these problems, doesn't it seem more likely that people would start porting the various linux libraries to BeOS? The end result would be the same really, but to assume that linux would be the better solution to start building on is probably incorrect.
  • Oh no, there is definately innovation. That's not the problem.

    The problem is that the innovation never gets accepted by the community at large. These innovations may be seen as too "unlinux" or "ununix". Because of that, even though they are better ways of doing things.... they get ignored and eventually die out.

    The only way to thoroughly kill an opensource project is to ignore it.

    -Chris
  • you want a capable file manager. use ls -R and navigate. I have rarely ever found any gui "file manager" even remotely useable. I cringe every time I see one of my users or staff trying to do something in "NT Explorer". Its useless for god's sake. les see, les spend 20 minutes point and click, associate a damn extension to notepad to find out what the fuck some other programmer was doing and then struggle with a damn gui editor when all you want was to cruise through a few lines of code to see if that was the damn file you wanted to see in the first place. A good command line shell will save you more hours than you'll spend learning how to use it. Don't give me this I just want to get my work done shit either. If you are IS/IT/MIS/programmer that don't cut it at all. Put the time in to learn to use tools that people have worked years to perfect not the "I don't want to learn what ls -R|more" means or ls -R | grep "filename.h" does. just time yourself sometime. how long does it take to type in ls -R|grep xxx.h and then how long does it take to click this directory, that directory, another directory. oh! we're getting close, click this directory.

    i ain't even going to apologize for the 4 scotch rant :)

  • Because its default file format is obfuscated and proprietary, and requires someone else to have either their own copy of Word or a special limited-purpose reader, and is difficult on anything but a Mac or Windows-running PC.

    That's lunacy? Sorry timothy, but methinks either your definition of lunacy has a very low threshold, or that you're a tad hysterical. Only readable on Windows and Mac machines? Fair enough assessment, but then again, that is some 95% of the desktop market.

    I also think your analogy is a bit incomplete. It's like having an x-ray machine whose default output is proprietary, and is only readable by another x-ray machine from the same manufacture (ok, ok, I'm torturing the analogy quite a bit, I admit it), but this x-ray machine also has alternative methods of producing output with most/many/all of the same features, or even a sort of fail-safe mode with the information expressed in a standard, basic format.

    I suspect I can still read a Word document in 20 years. Thirty? Who knows. But I suspect that in 100 years, we'll not only be unable to read present day word documents, we'll also be unable to read present day RTF, HTML, ASCII, etc. Media degrades, y'know. I think we have more important things to worry about over the next century than a particular file format, of all things.

    I appreciate and respect your ideal of a open file formats, but if Microsoft wants to make theirs proprietary, that is their choice after all. There are open alternatives, and their reluctances to use them may well bite them in the ass one day. (I also fail to see how an open BeOS will lead the charge toward such openess of formats. Elaboration, please?)

    Whew. I hate going on that long. Sorry 'bout that :)

    -T.A.F.
  • by Density_Altitude ( 250074 ) on Friday December 15, 2000 @07:36PM (#555115)
    I strongly believe that the best strenght of the GNU/Linux OS is that pepole using it are not clueless endusers. We are definitely different users, using a different OS. We build good/stable/secure linux systems because we know what we are doing. The reputation of linux is strongly based on that fact.
    As linux will gain shares of the desktop markets, I fear this reputation will dissapear...
    Furthermore, because of the graphic/multimedia nature of the BeOS I think it would be a much better fit for the desktop, especially if it become open source!


    --
  • by GandalfGreyhame ( 166871 ) on Friday December 15, 2000 @07:41PM (#555117) Homepage
    Blargh! What is it about open source zealots who fail to reason and who fail to even do one IOTA of research on the subject? Open sourcing BeOS just isn't going to happen. To quote Tom Maddox, Listmaster at Be
    I'll probably regret posting this, and doing so goes against the advice of my fellow co-workers, but there's a very good (and oft-stated) reason why BeOS in general and Net+ in particular cannot be open-sourced: we have legally binding contracts with the makers of proprietary technologies we use which forbid us from releasing their code into the public domain. Even mentioning making BeOS or Net+ open source sends our corporate counsel into hysterics.

    It ain't gonna happen.

    .http://www.escribe.com/software/beuserta lk/m40678 .html [escribe.com]

    So, this is another case of nVidiaism. They have contracts with other people which disallow them from opening the source. Stop bickering about it. Stop dreaming about it. It just ain't gonna happen.

    Even if it could happen, I wouldn't want it to. All you linux zealots would dive in and try and start 'fixing' things. Then we'd get a "microkernel" as large as that monolithic piece of shit linux 2.4.0.

    -G
    BeNews Editor

    Linux is only free if your time is of no value

  • The one thing that every (and I do mean every) existing OS designer and developer would kill for is the chance to do their work without an installed base so they could innovate. The tragedy of Linux is that the first really popular alternate OS was built by a community who's sole goal is getting an installed base even if they have to grab somebody elses. The end result being a non-mature OS with a thirty year old stack of legacy installed base compatibility to lock themselves down with.
  • If Be was going to even stand a chance, they'd have to come up with a mascot as cute as Tux.

    I just don't see that happening.. unless they used a porcupine that, instead of needles, had pixie sticks. I love those things.

  • Be.com is running open bsd because its the right tool for the right job. The BSDs do a far better job of serving than anything else right now, and probably will once the BeOS Networking Environment (complete rewrite of the network stack) is released too. You wouldn't use a BSD to edit video, you don't use the BeOS to do heavy serving. Note though that BeOS does to a very decent job doing moderate serving, for example BeTips is served entirely using BeOS.

    -G

    Linux is only free if your time is of no value

  • by sabre ( 79070 ) on Friday December 15, 2000 @07:57PM (#555130) Homepage
    True.

    But you are missing one exceedingly important point:

    Linux != UNIX

    In so many ways, from the kernel not implementing all of POSIX (only the "nice" or "clean" stuff), to the user space apps having a distinctively different feel (than say Solaris), Linux is significantly different already.

    Linux is different enough to break a lot of stuff that depends on system installs, and each distro is different enough to make packaging a bitch. It is not, however, different in the ways that are valuable. Linux distros are all just variations of a theme.

    I hate to say it, but it seems like Darwin of all things is one of the most creative things in the "scene". Hurd is probably close, but it's doomed from the start by being associated with "microkernels" (see my comment about killing/hindering a project by ignoring it). Unfortunately for Hurd, for example, they will not have the neccesary developer base to get the ball rolling and self sustaining for a long time. By that time, Hurd may very well be obsolete.

    So here is my battle cry: Lets try new, INTERESTING, things, and lets do them in the Linux context. Lets not break everything by changing something. Lets try providing extensions to Linux, and see how they work out. If they don't work out well (because they are inelegant, not because they are unused), then rip them out. If they work out well, keep them in, and start using them.

    There are so many good projects laying around, that are predominately dormant, that would be interesting to pursue. A completely random example that just popped into my head is the ill fated (killed by the fbcon hack) GGI project. Another interesting project is Berlin (http://www.berlin-consortium.org?).

    What would happen if these projects had a significant hacker base to draw from? GGI is much more powerful and interesting than fbcon, and we NEED something to take the baton from X.

    Anyways, enuf ranting. :)

    -Chris
  • no it's real, Be is currently in deliberations as we speak. They are teaming up with Opera to release a free (as in software) distribution that will be sent out with AOL cd's. [LIE MODE OFF]
  • Marketshare!=success. Even if they gained 100% market share, if they're giving away their product they won't make a cent on it.
    --
  • my favorite missing feature in pine ;)

    Hey man.. go grab nano [nano-editor.org], a clone of pico, it rocks man.. it is so great, it has search and replace, go to line (the two big ones) and a couple of other cool features. It even has a "pico emulation mode" where it looks and acts exactly like pico. So if you don't want a multi-megabyte editor or an editor with obsficated key commands, go grab nano.
  • OK. Flame retardant suit on.

    It would be, just, the greatest thing. Unix/Linux/BSD could get on with what they were designed to do, be a multiuser operating system. We could all concentrate fully and properly on what ought to be everyone's number one concern: Making DAMN CERTAIN Win2K server/advanced server/datacentre server never gets a foothold. Keep that damn thing on the desktop, at most.

    Use all these vast quantities of effort currently going into, well: making X do things it was not designed to do; trying to get open source drivers for video cards and having to reverse engineer things; ditto sound cards; in fact anything to do with persuading very good server operating systems to work on the desktop.... And point it towards doing great things server side. Let's see a damn good debugger for Zope; Some clever stuff to do with hot swap PCI; Lots of top notch hardware failure tolerant work; Innovate, dammit, you know you can.

    And with the people that want to squeeze that last 5 fps? Or those who want to make nano-small virtual machines for running applets etc. Fine. Good. Great even. Use something that was designed for it from the ground up.

    I guess that's the point. An open source Be would be just wonderful on the desktop. Unix is just wonderful on the server. Wouldn't it be great to use the right tool for the job?

    Here comes the napalm....

    Dave :)

  • You're making the assumpotion that the only reason that someoen would develop an OS would be so that they could create the **best* OS on a technical front.... maybe open sourcing BeOS would create a better" OS, but Be,inc, the driving force behind the BeOS would not... and that'd be detrimental to the BeOS in the end. How would be stand to make money? Who'd pay their architects to devise improvements to their OS?

    Yes, LInux has grown under the open source umbrella, but it still remains quite a few leaps and bounds from the reformity that BeOS possess...

  • by maggard ( 5579 )

    Be was going to revolutionize the world: It didn't.

    Be was going to sell the hottest boxes: They stopped.

    Be was going to challenge Apple on their own hardware: They didn't.

    Be was going to be THE "Multimedia OS": Disapeared from sight.

    Be was going to take the x86 world by storm: Not even a breeze.

    Be was going to break down the initial-investment barrier by releasing a no-price version: Nobody cared.

    Be is going to become an important embedded OS: We'll see.

    Fer goodness sakes - they can't give it away, why is making it Open Source gonna change things?

    A couple of headlines, a two-day wonder, a surge in downloads then pretty much the same things that's been happening all along to Be - not much. First it'll get picked over for whatever goodies can be gleaned from it, a few more zealots will join the Be camp, a couple bug-reports will be sent in, several even with a pointer to the relevant code. Beyond that - snoozer.

    There are lot's of kewl OS's out there ranging from LISP machines to Oberon to nano-kernels - nobody cares .

    Be does offer more then the typical niche-OS but nothing so incredible it's a must-have. It doesn't scratch any itch that can't be scratched otherwise. It doesn't offer any dramatic price or performance benefits that can't be papered over with the standard quantities of green-stuff. It isn't a developer's-dream or a user's-delight or an administrator's-joy: It's nice enough at all of these but it's not so outstanding at any of them to make it an imperative.

    Worse yet it's a horse in an increasingly crowded field. Aside from the MS stable of OS's (what - a dozen or so variations out now?) there's of course the Linuxen, various BSD's, Apple's dark-horse Darwin/MacOS X, QNX, and a couple of bajillion boutique & school-project OS's. Be is just one more small-OS trying to make the jump to the big-leagues.

    More power to it but Open-Sourcing ain't gonna be the break that makes it all happen for them. A half-dozen commercial OS's have been Open Sourced in the past year or so & none of them have benefited greatly from it. Heck, Apple even packages their Darwin for x86, a platform they're not even on & the active outside developers on it can be counted on one hand - a maimed hand at that.

    I honestly like Be - they've got some great stuff, but I just don't see them getting much out of Open Sourcing, certainly not enough to chance chance eroding their existing advantages. It may be A Good Thing in the big order of the universe but in the pay-the-bills world it wouldn't seem to be a prudent move for them.

  • Why does this very comment always come up whenever anyone mentions GUI-anything!!

    Say you have just downloaded 100 pics off your digital camera, and they're named pic00001.jpg through pic00100.jpg - and say you have a GUI filemanager with thumbnail display of graphics... tell me, how is your CLI going to help you pick out the 10 pictures you took of your dog faster than I can point and click on the 10 icons with a little picture of my dog inside them?

    Tab-completion only works when you have files with dissimilar names.

    Grep only works on text files.

    Ls only works if you don't need to preview your files in any way - I guarantee you it's faster for me to double-click on 20 different mp3s to hear the first few seconds than it is for you to type (including tab-completion) mpg123 St[tab]n[tab]*beep*[ctrl-D]G[tab]-Girl[tab][enter] . Same goes for images.

    Not to mention being able to select many files with vastly different names (such that wildcard globbing wouldn't work) and manipulate them - there's another operation where GUI filemanagers are a definite plus.

  • I was agreeing with everything you said till you got to

    lots of decent stories out there getting rejected, just look at k5, it's pretty decent

    kurroshin fuckin' sux. it is the most boring, pedantic, bombastic, navel gazing drivel imaginable. 100% philosophizing, 0% news. Yes, sometimes slashdot runs out of interesting things so they run some Katzian bullshit or some BeOS bullshit, ok: but don't compare it to kurofuckingboremetodeath. Who are you, signal 11?

  • I suspect I can still read a Word document in 20 years. Thirty? Who knows.

    Well, if you still have the computer you used to create them, or some equivilent, then that's probably a good bet as long as you use a storage medium that'll last that long. Otherwise, i sincerly doubt it. Thanks to MS's obsessive alteration of the .doc format for each new revision, it is often diffecult or impossible to load older versions, especially with any complex formatting, such as tables, frames (or whatever they have now), columns, etc. They do their best to keep the old version import working, but i have personally lost quite a few doc files do to a newer version of word. No one expects forwards compatability, but lacking BACKWARDS COMPATIBILITY?

    If you really want those documents 20 or 30 years from now, i suggest you print them and put them in a cool, dry place away from sunlight. ASCII files will probably still work, too.

    -ben.c
  • Okay, here's another example: http://korbit.sourceforge.net [sourceforge.net]. (disclaimer, I'm a lead developer on the proj).

    I'm trying to point out that innovation in neccesary for Linux to not become stagnant. Just like you said, we don't want to copy windows. We want to take the small subset of GOOD ideas from windows and run with them.

    I think that linux is doing an awesome job in the realm of simple web/dns/file servers... but that can also be done by a set top box. Lets try doing something interesting, and lets push the envelope a little bit.

    A lot of very interesting projects get killed way before their time because they are preceived as being too slow. Hell, with an expodential increase in computing power, do we really need to care about each clock cycle anymore? Isn't it more useful to concentrate on getting INTERESTING things done pretty well, then something BORING done way too well?

    Sure sure, you can optimize things all you want, and in many cases optimization is a very good thing. Optimization, however, is best done by computers: for example the compiler level, or done at a very high (Design) level by people. Microoptimizing every detail of a system is not only silly, but it is broken.

    Scratching the itch is definately what drives the linux community, but it is also what holds it back in some way. Being driven to fix particular incarnations of problems in software is a wonderful way to limit your thinking to what is "inside of the box". We need people to think outside of "what is accepted" and we need people to listen to them when they do.

    I know that I have some fairly excentric views here, but they should be voiced.

    Maybe I'm just getting senile in my old age. ;)

    -Chris
    http://www.nondot.org/~sabre [nondot.org]
  • > But you are missing one exceedingly important point: Linux != UNIX

    You're right, of course. But I still have to mention this interesting symptom of shifting attitudes:
    When asked by a reporter why Sun's new clustering software was restricted to Solaris and not available on Linux, McNealy's aggravation seemed to peak. "You people just don't get it, do you? All Linux applications run on Solaris, which is our implementation of Linux."
    Spotted at Linux Today [linuxtoday.com], which was quoting FUD^wZDnet in turn.

    --
  • by commandant ( 208059 ) on Friday December 15, 2000 @09:20PM (#555179)

    Linux and BeOS are made for different sorts of people. BeOS is to Unix (Linux in particular) what MacOS is to Windows, in terms of simplicity of interface. We won't get into superiority arguments between Windows and MacOS users.

    BeOS does not follow standards that are close to anything in the Unix world. In fact, now that I think about it, MacOS X seems to be a lot like BeOS. People who use Linux want a free, light Unix to use on their hardware. People who use BeOS want MacOS with bash.

    I don't think GPL'ing BeOS will change that. For most people, the attraction with BeOS is that it is so foreign... I have been quite curious about it. However, there is a cost-free version available for download, and it will even install itself in spare partitions if you please. Freedom to modify the code will improve userbase very little.

    Of course, I'm talking only about workstations and servers here. Maybe it turns out that BeOS is remarkably scalable, and fits well in the embedded world. This will of course change the prospects of Linux making it into embedded electronics.

    I do not belong in the spam.redirect.de domain.

  • But thats the point!
    The average user i.e. someone like me, or my wife wants something that CAN do everything. It doesn't HAVE to do everything well, but it DOES have to do it REASONABLY well. Windows has that, MAC has that does any other OS?
    I don't think so.

    I DON'T want to dual boot, I want to use a single STABLE (sorry windows) OS that has lots of app's. I (as an average user) DON'T GIVE A SHIT about who owns what, what license it's under (almost true,i care, but if I really want the software, the license is irrelevant, even though I usually disagree with it) but I do care about cost, stability and USABILITY.

    Bloatware, BSOD's, and incompatibilities are the BANE of modern software. These "features" are what causes people to stick with what they're given, cause, it's easier, AND 'cause there really isn't much of a difference anyway!

    *CAVEAT** Written from the viewpoint of Joe Blow User and His Wife Jane.
  • by Shin Elendale ( 132746 ) on Friday December 15, 2000 @09:26PM (#555183) Journal
    Well at least it isn't "Slashdot: News for trolls, stuff that mattered a week ago"

    -Elendale

  • Isn't be already competition to Linux because it is already in the same market, that is, the OS market? Linux and Windows are considered competitors, so why would Be have to wait to be GPL'd for it to be considered a competitor to both?

    Just because Linux is open source it doesn't mean it's in a special class of it's own - it still has maintenance and other costs associated with the TCO that Windows and Be have associated with them.

    Linux developers should think this way because if they did, then Linux would be much easier to use than it is now.

    Cheers,
    Daniel.

    --

    Daniel Zeaiter
    daniel@academytiles.com.au
    http://www.academytiles.com.au
    ICQ: 16889511

  • But you are missing one exceedingly important point:

    Linux != UNIX

    Actually, that Linux != Unix was implicit in my point. If Linux == Unix then it would have had an installed base as a cost of that decision. The fact that Linux != Unix is precisely the tragedy. Since it isn't Unix it didn't need to inherit all the baggage but instead of throwing all that legacy out and looking for new ideas, the community embraced the legacy as a shortcut to "legitimacy".

  • I don't like the idea of someone modifying my code and not showing me what they did.
    The GPL does not help all that much with this problem. If MegaCorp use your code internally they can hack the crap out of it (or fix it ;) and no one else will be the wiser. The GPL only helps if they try to distribute.

    And anyway, sometimes you have to let your work go. If you want to do more than one or two things for the OSS community you often need to leave it to others to take up your work whilst you go and do something else. Bit like children. You just have to let them go. If the code's any good and the function compelling enough it will leave you anyway (yes including Linus and the kernel he started). Get over it.

  • The point being that they actually tried a different naming heirarchy... wow.

    Far more than that - have you seen NetInfo? ...wow.

    --

  • Excellent point, hidden in there somewhere. Yes, Be OS does use a different windowing system, and from what I understand (I don't know much more than you do), GTK+ has already been ported. Mac OS X also uses its own windowing system, which will certainly become more popular, but Mac OS X's GUI is closed-source, much like Be OS today.

    --

  • Documents in (even half-decent) HTML

    I just want to point out that the reason there's so much bad HTML code out there is, HTML was never intended to express attributes of page layout, or really, physical appearance at all. A standard word processing program these days does more than process words; it also allows you do do desktop publishing, choosing the precise layout of your text and other elements. Trying to force layout into HTML is a difficult hack to accomplish at times (peruse my home page if you don't think I know what I'm talking about).

    HTML is not the standard format that will replace Word's proprietary format. Microsoft wants a hacked-up version of HMTL to replace it, primarily because HTML has become a buzzword of sorts, but then you run into exactly the same problem with reading that format that you now have with Word - you'll need either Word or Internet Explorer in order to read it properly, because it will break all the standards and specifications the other browsers strive to adhere to.

    I don't have the answer. I just know that HTML isn't it.

    --

  • On a user level, you are totally correct: Linux hasn't benefited at all from BSD competition. And BSD hasn't benefited from Linux. I think a large part of this, though, is that neither one has any major improvements over the other. Both do about the same thing in about the same way. There's sure to be people who say this isn't true on both sides, but I'm pretty sure they will be highly grizzled developers, not higher level users. After all, nearly all the ideas in BSD and Linux came from the same seed.

    In any case, BeOS does have some major differences, so it would naturally bring new ideas into the mix. At this point, I think that would be a very good thing.

  • by localman ( 111171 ) on Friday December 15, 2000 @10:34PM (#555205) Homepage
    I think opening up BeOS would be pretty great, but I don't like this mantra that "competition is always good", because it's not. Just look at the wonderous results of the browser war - there have been hardly any improvements whatsoever in web technology since that competition started. And how about the original fracturing of UNIX? Competition is only good if all the players are honorable and open minded - aiming to win by being the best for the users. Otherwise it just turns into a snakefight.
  • Be already has most of these things:

    High-quality word processor - Check...(Gobe)
    Spreadsheet - Check...(Gobe again)
    Good web browser - Not completly ready, but hows opera 4.01 sound?

    Add these together, with a few great high end apps, and many apps ported from linux, and you end up with a hell of a good OS, even for newbies. With the new BeOS networking and OpenGL, I see no reason at all why Be should not be a great OS, for anyone. IMO, Linux could learn a few things from BeOS, and vice versa. BeOS could teach linux how to be good on the desktop, and Linux would teach Be how to be a great Multi-User OS, which is the only thing that appears to be lacking from Be. The apps will come, eventually. I could use BeOS 100% of the time already, if it werent for games. I sense a new wave of game development ahead though, because of the new OpenGL implementation in Be, which is BTW faster than either windows or linux, and has no drop in framerate even when running in windowed mode. :)
  • Why does it matter to us what works best for you? So we can make what we have better. Obviously, you use Be OS because it's better than the alternatives. Bringing some of those alternatives up to the same level would benefit everybody.

    --

  • by drmastermind ( 264294 ) on Friday December 15, 2000 @10:52PM (#555211)
    Besides the fact that BeOS isn't going to be GPL'd anytime soon there is also the fact that that BeOS and Linux were created to do two compleatly different things.

    BeOS was developed as a multimedia OS, and Linux was developed as a Server OS. The optimizations that are required for one would destroy the other. ie you can have the kernel doing the majority of it's processing with a video render or have apache running at full speed.. not both.

    To paraphrase the perl advoticy article... there is no one OS for every task. Just like PHP is easier than Perl for certian projects, BeOS is easier than Linx for certian tasks.

    To clarify for our non-geek readers... Both a hammer and a screwdriver will put a screw through a board... but only one was designed to do so..

    Dave
    btw: no I can't spell... I code for a living

    Whats the point of being grown up if you can't act childish sometimes? ---- Dr Who
  • Which graphics card did you get that BeOS doesn't support?

    Writing graphics drivers is really icky business. Even when you do have documentation, it is frequently cryptic, and missing important bits. Even docs from Intel, which are about the finest I've seen anywhere, often omit small details (like the formula for calculating the coefficients for the pixel clock PLL).

    Don't have documentation? Congratulations, you're SOL, and reduced to disassembling the BIOS ROM, or picking through the source code contributed to the XFree86 Project. And if you think having XFree86 source code makes driver writing cake, you may care to have a look at the v3.3.6 code for the NVidia GeForce, or the v4.0 code for the SMI Lynx (which has whacking great bugs in it). Or best yet, the code for the NeoMagic laptop chips. (Note that this is no slam against the XFree86 guys; I'm just pointing it out that it's not a panacea.)

    There's tens of thousands of Linux contributors. There's only 100 or so people at Be, who really are dancing as fast as they can.

    Schwab

  • You do not need to see the source code to the BeOS kernel to write drivers for it. In fact, our device driver API is dirt simple. You can read about it here [be.com].

    In fact, you can find programming documentation for all of BeOS [be.com] on the Web site.

    Schwab

  • Here's an interesting idea: If there's a feature in BeOS that you like, why not implement it in Linux? There's nothing about Be's code that is so earth shattering that it couldn't be replicated with a little ingenuity. The problem with implementing some of Be's features in Linux, such as their unique file system, is that it would break compatibility.

    Linux is still a Unix clone and has all of the benefits and shortcomings thereof. And before you get on your horse and claim "BeOS is based on Unix too!", it is not. Nor is it based on Linux, BSD or any other clone of Unix. Be did implement a Born Again Shell so BeOS could run most POSIX compliant programs. However, that's where Unix compatibility ends. BeOS was written from the ground up, including the kernel, with performance in mind. From a programming perspective (I have over 25 years experience, I might add), BeOS's API wins hands down over all other major operating systems. As for BeOS's lack of drivers and applications: Anyone with technical knowledge of the hardware can write a driver for BeOS. There is documentation on Be's Web site and many examples, BeOS and the development tools are free for the time it takes to download. If there is an application you would like to see on BeOS, by all means write it!

    I personally don't think either BeOS or Linux would benefit from BeOS being GPL'd. In fact, I think that BeOS might suffer from too many ingredients in the pot. For example, if I install Red Hat using the "Gnome Workstation" option, it takes up somewhere in the neighborhood of a gigabyte of storage space. This is heinous bloat, most of which the average user (or even programmer) would never use. But trying to make heads or tails of what packages are actually needed would be impossible for the non geek.
  • What if lawyers suddenly became honest?

    Imagine if the legal sharks out there stopped pursuing lawsuits that are based upon dubious claims and wholly intended to make their clients a fast buck? What if they suddenly became ethical and just flat out refused to work for companies like Rambus? What if socialists who are busy in some cities suing firearms companies, for supposed damages because hood rats are using guns to kill each other, just couldn't find a lawyer worth snot to pursue the case for them?

    Guess what, it ain't gonna happen so why waste time wondering about it?

    Or how about this, what if D-O-G spelled cat?

    Lee Reynolds
  • It's not possible to GPL what remains proprietary from Be (because of it's partners, or because it would require substantional engineering effort to clean up the code for release, that is: someone must pay for it to happen). However, the source code that most developers desire, the Tracker and Deskbar is available on http://www.opentracker.com. And the developer tools are not limited to the professional version either.

    To quote from Be's website:

    However, Companies who develop software for BeOS desktop PCs are encouraged to take advantage of free resources like BeOS Personal Edition, BeOS development tools, and more. It is possible to create quality BeOS software without paying a dime.

    If you think there's no applications, check out http://www.bebits.com
  • unlike linux which was based on 70' technology that was based on using text based dumb terminals.

    And I suppose you drive an electric car because petrol engines are 100 year-old technology.
  • And darwin is just FreeBSD with apple sauce.

    That's not exactly true. Darwin can handle multiple forks on file systems that support it, uses a Mach kernel and most importantly has a great innovative driver framework (IOKit), designed for support of Firewire and USB (hotplugging, dynamic loading and unloading), which both don't work well with Linux.

  • Maybe it turns out that BeOS is remarkably scalable, and fits well in the embedded world. This will of course change the prospects of Linux making it into embedded electronics.

    Be is already putting a lot of effort into the embedded market (perhaps more than developing BeOS itself for the PC). Ever heard of BeIA [be.com]?

  • theres 'find' and then there's 'locate'
  • Linux has Linus. Linus is great a holding an open source project together. He's brought us the penguin, the goal of taking over the world, and the sound clip "I am Linux Torvalds and I pronounce Linux as Linux." He has a certain "Internet charisma" if you will (he may also have the more traditional type, but I've never met him, so I couldn't say). This, more than any other single factor, is why Linux has suceeded where Mozilla, HURD, and so many others have staggered.

    So what happens if you open source BeOS depends almost entirely on how good the guy who leads GPL BeOS. I'm not trying to say that Linus is the only one who's done any work on Linux (indeed, as many of you will hasten to point out, most of "Linux" doesn't even have anything to do with the kernel), but he has been responsible in a large part for keeping people interested in the OS, and getting them to help out. It's just like a business. You've got crappy management, it doesn't really matter how good your product is.

  • 1. BeOS and Linux made more compatible and make them able to run each others binaries.
    2. The focus of Linuxdevelopment is moved to serverapplications, while BeOS takes over as the GNU desktop-OS. Also try to move them towards a common Windowing-system, common tools etc.

    Market the two as two sides of the same thing. GNU/Be (Try to pronounce it), the desktopOS and GNU/Linux the serverOS.
    Kind of like Win98 vs. WinNT, only both much more stable.

    I do believe in Linux as a desktop-OS, but we don't have the best foundation available.
    Now.. BeOS will not be GPL'd anytime soon.
  • by Anonymous Coward
    Heresy! X is tradition, dammit. We can't break with tradition. We have to keep X with its gaping security holes, its unpredictable behavior, and its massive code-bloat. We can't do anything new, because that wouldn't be traditional. Screw the non-techie users. We don't want Linux on the desktop anyway, that means people who aren't hard-core geeks could use it, and we wouldn't be 1337 anymore. Jeeze, what the hell are you thinking? Abandoning X and going with something new that works would break with tradition, and we all know that violates the cardinal tenets of the Church of *nix. Remember the First Commandment: Change is bad in the *nix world.
  • Is BeOS really all that better a platform to develop on then say, Windows? I know this is heresy but Visual Basic, Delphi, etc. make it E-Z to code for, the tools & support for C, C++, etc. are all very well-developed & mature. Heck, Next had a fantastic development system but really couldn't get it out there 'till they took over Apple for -x million.

    As to using, all of the folks who I know that have actually used Be for any length of time have raved about the OS but lamented that it wasn't really applicable to them 'cause it didn't do everything they needed. At least in the various *nix camps it's getting to the point where one can run in it most of the day & reboot into the other OS only occasionally; isn't it worse for the Be folks? (Be-en?, Be-ites? Be-exxians?)

  • I also think your analogy is a bit incomplete. It's like having an x-ray machine whose default output is proprietary, and is only readable by another x-ray machine from the same manufacture (ok, ok, I'm torturing the analogy quite a bit, I admit it), but this x-ray machine also has alternative methods of producing output with most/many/all of the same features, or even a sort of fail-safe mode with the information expressed in a standard, basic format.

    I'm just pondering what an ASCII X-ray would look like :-)

  • I'm not a BSD user because developments like MacOS X make me uncomfortable. It's an ideological difference. I don't like the idea of someone modifying my code and not showing me what they did.

    As far as I know Apple has published the source to all the BSD stuff they have touched. The closed source parts of OS-X are things they wrote in house (like DisplayPostscript, er, DisplayPDF I mean, the OS 8 compatability box, and the candy coated GUI).

    That is pretty much like the TiVo people giving back the few Linux kernel mods they did (I don't think they gave back the filesystem, since they use a kernel loadable module there, but I donno for sure). I know they don't give back their candy coated GUI. A shame, because there are a few little tweaks I would like to make...

    Yes, with the GPL you are required to give back changes in many cases. With the BSDL you are never required to give them back. So Apple is either "being good people (at long last)", or "playing the PR game". TiVo is "walking the fine line guided by their lawyers".

    Does the TiVo make you uncomftrable?

  • Uh... well, we mention the CLI because, as you GUI zealots should know, you can't do this with a GUI: ls pic000[01]?.jpg | awk '{ system( 'mv "$1" cat_"$1" ; convert -geometry 160x120 cat_"$1" thumb_cat_"$1 ); }' And, yes, I do this sort of thing *all the time*. I hereby predict that the next big paradigm shift in user interfaces will be back to the CLI -- only the CLI will understand natural language, and may be hidden behind voice recognition.
  • You've just compared three different OSes. That's like saying, "If ham is so much better than turkey, why are you eating veal?"

    Could it be that, while BeOS is better than Linux, OpenBSD is better than Be? That would account for the situation you just described. Or, possibly, they all have their advantages, and OpenBSD just happens to be the best OS for serving up their website.

    Get a clue.

  • If BeOS would be distributed in an OpenSource or GPL license I think it would cause little impact on Linux. What really would cause it may be a boom on multimedia, together with all *NIX.

    BeOS is clearly superior to any other OS in terms of multimedia. The fact it is free for the masses is already a big +. However I suspect that this hampers some threads of development. Specially integration with other OSes. If this barrier would be overturned then I believe we could see BeOS suddenly appearing as a *NIX visual interface. There are lots of things on *NIX that demand good quality graphics and sound. And *NIX is surely not the best for that job. Even Linux still looses a lot here. Having the BeOS sources. people could try to overcome these limitations by combining tasks between *NIX computers and BeOS. BeOS is probably the nearest OS to *NIX in this field so that integration could be quite powerful. Imagine a powerful Beowulf cluster calculating 3D virtual worlds and BeOS stations showing it... Yes it is possible now. But still I believe that open source would make a much better job. Specially on what concerns kernel interaction. Clusters could be more tightly integrated for example. Maybe BeOS would be not a station but a cluster member with different tasks.
  • Just an aside:
    ipf and iptables are both branches from Darren Reed's ipfilter. One could get ipfilter up and running on a Linux box before, but now it's in the kernel and rightly so, in my humble opinion.

    The big difference in iptables and prior linux firewalls is that ipfilter is a keep state firewall meaning that one doesn't need to keep track of TCP/syn, TCP/syn+ack, TCP/ack flags to "guess" a genuine connection's status.

  • Yeah, well have you seen RedHat's lately? Not exactly a hot commodity.
  • TIVO is doing a little more than they are actaully required to by the GPL.

    Anyone who wants to can download TIVO's kernel mods, but the GPL really only requires them to give it to people who have the binaries.

    If TIVO wanted to be jerks, they could require you to send in the UPC code for your TIVO before they would mail you a floppy disk with the kernel code on it. Of course, that would actually be more work for them, and it would be bad press, so there's no advantage.


    Torrey Hoffman (Azog)
  • DOS -> WINDOWS

    Can't argue too much there.

    or DOS -> OS/2 -> NT

    Wrong. DOS was not the foundation of OS/2. OS/2 had a layer that could emulate DOS calls when the programs were run but it was written from the ground up. I'm not going to argue too much on NT taking from OS/2 as many parts were canabalized like the filesystem but NT is a different horse with a very different design.

    or MULTICS -> UNIX -> MINIX -> LINUX
    BeOS is written from scratch with out all the age-old crap underneath. I'd say in the time they've been on x86 and the rate their gaining that Windows AND Linux just better stay the fuck out of the way.

    Many OSs have been written from scratch. Technical supperiority does not lend oneself to being the market dominator. I believe market dominance has more to do with how many apps users want or need are avaliable on that OS. The free/open source OSs are the exception as many users wrote the applications they wanted. What is the BeOS's killer app? It might be a great OS but without a killer app it has no future.
    Molog

    So Linus, what are we doing tonight?

  • I think we have more important things to worry about over the next century than a particular file format, of all things.

    You are saying that preservation of historical documents is not important? I would bet that even now there are Word/WordPerfect/WordStar/etc documents being trashed because people just don't have the time to hunt down the proprietary viewer to read them.

  • TIVO is doing a little more than they are actaully required to by the GPL.

    More then required by the GPL and the binary module exception, yes.

    My point wasn't that TiVo are bad guys (I don't think they are), but that what Apple is doing with BSD is pretty much the same thing TiVo is doing with Linux, so if one doesn't like what Apple is doing, don't think the GPL on Linux saves it from the same fate.

    I do admit Apple could have done "worse", but that wasn't what the previous poster said. The were upset about OSX, and wanted to stick to GPL'ed things to prevent that.

    If TIVO wanted to be jerks, they could require you to send in the UPC code for your TIVO before they would mail you a floppy disk with the kernel code on it. Of course, that would actually be more work for them, and it would be bad press, so there's no advantage.

    Sure, and if they wanted to be jerks they would take a hard stance against hacking the TiVo and see if they could get all the bad press iOpener and CueCat got too. But they have the totally reasonable stance "if you open it and play with it that's cool, but if you break it don't call customer support for anything other then laughter".

    A shame about that no-ethernet and no-firewire thing though.

  • eeyes ~/.netscape/cache/*/*.[Jj]pg

    is that the command you were looking for?

    hope that helps...

  • A couple times a week I think it's "Slashdot: News that was on Yahoo yesterday."
  • Wow. BeOS actually gets mentioned on /. twice in a week? Something must be up. Is Malda out of town? Just kidding ;) Actually, this is a pointless subject. Linux users don't like BeOS because they feel threatened, and BeOS users don't like Linux because they envy their success. The partisans on both sides will keep spewing their rhetoric ("64bit FS, MediaOS, multi-threading, speed"/"focus shift, dead, non-OSS") and the conversation will do nothing more than to raise my blood pressure at the diehards on both sides who are unwilling to admit the faults of their OS. Without further ado, I'd like to throw my 3 cents into the ring

    Advantages of BeOS over Linux:
    1) It's faster. As someone who has used (and tweeked) most of the popular Linux distros, I can say that BeOS is certainly faster.
    2) It has more "creature comforts." Stuff like attributes on the FS, the simple API, and obsessive attention to details like good drag and drop, good interoperabiltiy between apps, standardized interfaces, etc, really shows up in the amount of polish the OS has.
    3) It scales. If you're an intermediate user, use the preferences menu for everything. With it, you can set up a telnet/NAT/ftp server with a couple of clicks. More hardcore than that? Edit the text files directly.
    /etc and vi are only a terminal away.
    4) It has a good app-base. A lot of the most common desktop usage apps are there, and a most of the apps are high-quality and useful. Also, almost all POSIX-text-mode apps are easily portable, so BeOS has ports of nifty stuff like compilers, language parsers, imaging libraries, and even full-blow subsystems like SANE. Plus, it has SAMBA, Apache, and dozens of other common *NIX apps. But wait, it gets better. There is an X server that is being worked on (on hiatus pending release of BONE and the new network API) and a port of Wine on the way. Lastly, BeOS currently rules the roost in terms of innovative audio apps.
    5) It is easier to manage. I see /etc and I barf. Ugly as an ape's ass. Modules.conf is a travesty in this age of Plug & Play. SysV initscripts are ridiculous. (BSD all the way! ;) modprobe? Why? In order to enable NAT on Linux, I have to recompile my kernel, edit modules.rc to load the ip_nat modules, and edit rc.firewall to setup the firewall rules and enable NAT. On BeOS, I copy the nat module to to net_server add-ons directory, I start up the configurator, use the defaults, and hit "Nat ON" And voila, it's on. To change my refresh rate, I go to the screen preferences and change it to a nice 85hz. In XFree86, I had to write a BeOS program that would get me the modelines and add a modline to XF86Config. Do you realize how many newbie Linux users are sitting there destroying their eyes because XFree86 doesn't think that their monitor can do 1152x864x85 (mine does that res at 90-something hz)? That's just wrong. To install ALSA, I have to edit modules.conf and give it a huge string of parameters telling it stuff that it should get from PnP anyway. In BeOS, it just loads and the only tweeking I have to do is what volume the mixer should be at. After recompiling kernel 2.4, I have to go to modules.conf and edit it to tell it that ne2k is a network driver. In BeOS, the cards are already detected and awaiting IP addresses in Network Prefrerences.

    Disadvantages of BeOS vs Linux.
    1) Linux will always have superior networking. BeOS just wasn't designed to put an emphasis on processes that simply move data around (TCP/IP stacks) and no matter how well designed the new network environment (BONE) is, the 3ms task slice (vs 50ms for Linux) and the pseudo/kinda/maybe realtime sheduling will work against BeOS here. But that's okay, its a client OS anyway.
    2) Linux (even better, FreeBSD) has superior filesystem performance. A process that simply moves data around the filesystem will get about 20% better performance on ReiserFS than BFS. That's okay too. Unless you're a file server, you don't notice the lowered performance. Again, the OS simply wasn't designed to put a priority on just moving data around. As such, you'll see Bonnie scores 20% lower, but with half to a third of the processor usage.
    3) It still doesn't have as many GUI apps. Browsers are limited to Opera 3.6.x, Netpositive, and Opera4 (soon, maybe) Of course, there is always Mozilla, and the BeOS builds are progressing everyday. Recently, BeOS has been getting some more support in the app area, and if BeIA pans out for Be (which those anti-BeOS idiots would know, if they ever read BeNews, has been getting a LOT of industry support) then we could be seeing more desktop apps out.
    4) It doesn't have as large of a developer community.
    5) Be's role in all this is iffy. The focus shift hurt, but if those anti-BeOS idiots would ever read BeNews, development on BeOS is far from stopped. Right now, there are the game_audio, OpenGL, BONE, and Java2 SE ports all being worked on. I can guarentee you the slate of distros being released with Linux 2.4 will not have all these updates.

    Then there are the ties. Of them, the most annoying is probably hardware support. Yes, BeOS supports less hardware than Linux. No, you can't buy any of that unsupported hardware outside a flea market. Aside from the 3D part of the NVIDIA chips present in all my computers, all of my computers have full support for BeOS. And this isn't all standard hardware either. My PIII motherboard is one of those MicroATX all-in-one jobs from a fly-by-night company. Hell, it took me half an hour just to find out who made the sucker. Yet, everything from the network chip, the sound chip, the graphics chip, they're all supported in BeOS.
  • A) No you don't need OS source. It's nice, but BeOS drivers don't live in a communal heap of code all take from the same source tree. (I always thought of the Linux driver thing as somewhat incenstuous. Its scary that drivers are all developed together and depend on each other.)

    B) You'd still need man hours to port all of the drivers. BeOS drivers are very different from Linux drivers.

    C) As I recall, the XFree86 license doesn't require you to redistribute code, so its not like any vid cards will get supported that aren't already.
  • I'd like to see an OSS BeOS too, with a tightly controlled development model like OpenBSD (to keep the small, fast, powerful, sexy focus) but like he said, it ain't going to happen. Even if Be wanted, a lot of BeOS is prorietory code (like the font rendering engine from BitStream, for example. BTW: Anybody hear what happened to the Font Fusion server BeOS was supposed to get?) On a morbid not, however, I would hope, that if Be ever goes under, they'd open the non-proprietory parts of the code so people could quickly fill in the gaps and keep BeOS going.
  • Yes, that is EXACTLY what has happened with OpenBSD. OpenBSD is such a failiure. I mean, a project led by purists concerned with stability, good god, what WERE they thinking?

    Give me a break. If BeOS was lead by a core team focused on keeping it BeOS-like, then it would kick serious ass.
  • 1) Be would rule the world.
    2) It's not.
    3) Slackware all the way.
  • by be-fan ( 61476 ) on Saturday December 16, 2000 @09:54AM (#555300)
    Yes excactly. That's what Linux is aimed at isn't it? GNOME and KDE are examples of "good" competition because they're trying to be best for the user? Not. It seems to me that a lot of "competition" in the Linux arena is just a pissing contest between developers. If KDE and GNOME were trying to be good for the user, they'd make a common binary API, and then duke it out over who could make the fastest/smallest/most feature filled desktop out there. Linux is turning into Windows as we speak. It already takes up as much RAM, and newbie type things are being installed that tries to trap growing users into using them. (One problem with both Linux and Windows is that they don't grow with the user. For example, instead of having scalable (to the user) set of initscripts, Mandrake 7.2 implements a hack that wraps a set of scripts over the standard SysV scripts. Ugly, inelegant, and totally confusing the the user who is trying to graduate from the simplfied ones to the real ones.) Every release (I'm talking about the upper stuff like Mozilla, X, GNOME, KDE, etc) is getting criminally bloated and features are added just for the hell of it. Linux NEEDS a competitive BeOS to keep it from getting fat and lazy just like MS.
  • It wouldn't make much of a difference. The BeOS microkernel and HURD are as different as fast and slow.
  • In my humble opinion, Be is greatly superior to both Linux and Windows. Before I'm moderated down as Flamebait, I want to point out that I have a triple-boot system, and have the experience in all three to make a pretty valid asessment.

    Windows is sort of easy, very popular, and has excellent driver support. If it was honestly as bad as people say, it wouldn't exist because people WOULD look elsewhere. Windows is at least good enough for the unwashed masses.

    Linux is an interesting experiment and a powerful *nix, especially for the money. The problem is it IS hard to use. Even KDE and GNOME only scratch the surface. It is a system built on a very old specification, and it shows. Users (not newbies, just users) want to use the system, not tweak it endlessly. Recompiling the Kernel, Libraries, and Apps to get good performance (mine sucked until I did the above) is time consuming, overly technical, and more than even many power user would be willing to do. Linux is a great *nix, but not a great Desktop OS.

    Be is the youngest and still has a ways to go, but it shows the most promise. I fear it will die off because of Windows dominance or a shift to IAs by Be, but I hope not. It is very responsive, contains no overtly legacy code, has an Object Oriented API, boots in seconds (while MS tweaks Windows to get 3x the boot time), and is very stable. The only reason I don't use BeOS more is its small Application support and the fact that I haven't figured out PPPoE on Be yet and I can't live without my DSL.

    I see an Open Source Be being disected and pasted on Linux (Bad Idea), being fractured as hackers paste on *nix concepts (Worse Idea), or being left to die by a community already focused on Linux (A Tradjedy). I hope Be makes it, but I don't think that the magic balm of OSS is the key. More likely Be would die a quick death as OSS, especially after the proprietary code (from other companies) is culled to keep copyright lawyers happy.

  • A) Not multi-user, big loss. To tell the truth, I really don't miss multi-user. Some might, but I can guarentee you that the average desktop user won't.

    B) Linux has crashed more often (devel kernels) than BeOS. What kind of stunt are you trying to pull. BeOS has been rock solid ever since DR8 (which was three or four years ago) Of course, it could be a problem with your hardware, in which case I suggest no buying a Packard Bell next time.

    C) The filesystem is fast (somewhere between ext2 and Reiser, closer to ext2) reliable, and feature filled. It has features that are still in the developmental stages for ResierFS. What more do you want?

    D) "emulated under Linux." That's the whole problem. The BeOS GUI isn't great because it looks spiffy, but it has a level of "Zen" unmatched by any Linux GUI. In Linux, it pains me to use the GUI sometimes. I end up just using xterm. But in BeOS, the GUI just feels so homey. (Of course, there is the terminal there too)
  • by be-fan ( 61476 ) on Saturday December 16, 2000 @10:10AM (#555307)
    The fonts are monkey-ass ugly. It is hard to configure if you have good hardware. (VESA modes limited) It is slow, and takes up an insane amount of RAM. The 40MB that X takes up on my machine is more than the entire BeOS does. The simple fact that X contains 20+MB of binaries is hideos given that its equivilent in BeOS is contained within the 3.1 MB app_server.
  • Actually, check out this page [gcn.com] for a nifty logo that Be should adopt.
  • The BeOS GUI is independant of the kernel. I hope you don't think that the GUI is in the kernel, do you? And if you'd actually USE the BeOS instead of look at benchmarks, you'd agree with the BeOS users. The truth is, that benchmarks are rare for BeOS and are a pain to write. That's why you don't see them. The sheer fact that you can run a dozen AVIs on an 8proc machine (see BeNews) and can do video mixing, and audio mixing with dozens of channels is how we know BeOS is faster. Try some of the BeOS (particularly the audio apps) and see if you can find some that work as well on Linux.
  • 20meg for a windowing server? That's criminal. That means that of the 40MB or so that Linux takes up on my system, half of that is X?
  • truetype fonts work wonderfully
    >>>>>>
    Well, they work. And uh, I can load them. And umm, it doesn't crash when using them... BUT, they look aweful, all jaggedy. And its not just the lack of anti-aliasing, X fonts genuinely suck. But they DO work.

    3d graphics are extremely fast
    >>>>>>>>
    No they are not. Even Windows 2000 (which isn't exactly the pinnacle of OS design) is 30% or so faster. And that's only because NVIDIA was nice enough to give X some pro-caliber drivers. (BTW, the NVIDIA drivers are around 20-30% faster on average than the stock XFree ones for 2D primitives)

    stability is good
    >>>>>>>>>>
    I'll give you that.

    X remote display works well even over a modem link
    >>>>>>>>
    True.

    and even the notorious X bloat has been put on a diet
    >>>>>>>>
    Wow. Look mom! I lost 200lb and I now only weigh 350!

    There are many well known defiencies, such as limited suport for drawing primitives, lack of alpha channel support, not to mention lack of dynamic resolution/ color depth changing
    >>>>>>>
    Which all other windowing systems have had forever

    but they are all comming down the pipeline
    >>>>>>>>>>
    Real soon now!

    Not to mention that it is still a bitch to configure and for something that has been worked on so much, it is quite underhwelming.
  • QNX Photon is small, fast, featureful, has great fonts, and has remote display to boot. In other words, it's every thing X should be, but isn't.
  • Oh puh-lease! That old chestnut about Be being unable to run on G3 Macs 'cause Apple wouldn't give 'em the specs - bullshit.

    A half-dozen other OS's managed the exact same feat before Apple started giving folks information: If they all could do it why not Be? Either Be's engineers aren't as hot as they profess or they're just trying to duck responsibility for their exiting that market. Of course that fact that Intel pumped in a big shot of funding about then and got a board seat wouldn't have had an influence, nooooo.

    As to Apple killing PREP/CHRP/etc. - what about Motorola & IBM? It was a troika - even if Apple knifed it's own baby the rest had their own projects that Be could have gone to.

    IBM was going to ship their hardware with OS/2 & AIX (and did ship - indeed at one point it was actually possible to get a beta MacOS release running on the IBM hardware.) To this day they're shipping nearly-CHRP motherboards one can buy, complete with PowerPC's. They're also using them in their own servers, every day.

    Motorola was subsidizing MS's port of NT and planning a big line of Mac-compatibles that would have been just prime for Be. Indeed Motorola took a big hit when Apple dropped licensing. Had Be produced a reasonable business plan Motorola would have been happy to cut their losses (and get revenge on Apple.) Be didn't & missed another opportunity. Again, one can today buy nearly-CHRP motherboards from Motorola, complete with PowerPC's.

    Be didn't cut it because they mis-predicted the market - over and over. Nobody wanted a "Media OS" that didn't have basics like a decent word-processor, nobody wanted something that was like nothing else. Be still suffers from not enough applications and no overwhelming sales features (a clever FS & lots-o-threads does not cut it!)

    Linux & the BSDs had a strong heritage to build upon & a ready-built community of CompSci students familier with unix & the wonderful GNU tools.

    NeXT had Steve Jobs, the VC money, and after about the same set of mis-steps Be made but ended up with a really stable OS that was very portable & a dream to develop on.

    Apple dicked around for 10 years & finally got bought by Next for a few negative-million bucks. Be never really had a chance against Next; it was sexy but had nothing to offer Apple but more of the same - another unique OS with limited compatiblity & an even smaller set of applications.

    Sorry - Jean-Loius may be a smart fellow and may have come up with a fine boutique-OS but he's no great success at running the company. There's been a series of opportunities that Be has missed & it's not showing any signs of getting savvier.

    Even going into the embedded market is a big gamble. As you noted, Linux et al is heading into the same place and with a whole lot more mind-share. QNX and others are already there - don't think they're going to let their lunch get taken from them without a fight either.

    Be is a neat OS but unless they pull a rabbit out of the hat they're down the tubes, fast or slow. OS-2 Warp was awesome also as it circled the drain.

    ps Other folks have the respect to stand behind their own words - loose the "Anonymous Coward" and come out into the light.

  • So what do you do on your Be box? I mean, if you're a Be developer that's hardly a real-world example.
  • A) I get the 30% from the tests AnandTech and TomsHardware did of the 3D performance between Windows2K and Linux. And if you get the same performance with Win2K and Win98 for OpenGL, then there is something wrong with your setup (Win2K is significantly faster for most OpenGL apps)

    B) I use Netscape6.

    C) XF86Setup won't help anything. I have no problem using xf86config, it's a perfectly user-friendly program. Even the XF86Config file is pretty friendlY (nicely commented) What my problem is that there is no setting that allows you to set your refresh rate, and X-4 is limited to VESA modes, which means that getting anything above 75Hz on your 1152x864 monitor means getting modelines. Of course, modelines have a 30page HOWTO explaining them, and not everybody has a BeOS machine they can access and steal modlines from. (BeOS autodetects monitor modes) Its a moot point anyway. XFree86Config only exists because X is too stupid to detect anything for itself. About the only thing that should be there is fontpath.
  • Are you sure? A context switch every 250 microseconds is pushing it.
  • by scrytch ( 9198 ) <chuck@myrealbox.com> on Saturday December 16, 2000 @02:40PM (#555333)
    > I'm not a BSD user because developments like MacOS X make me uncomfortable. It's an ideological difference. I don't like the idea of someone modifying my code and not showing me what they did.

    This is by far the most inane argument I have ever heard in terms of OS choice. Perhaps you prefer linux because of ReiserFS, or its support of your hardware, or perhaps another chooses BSD because they prefer its style of system management or toys like netgraph. Or Solaris for its scaleability, or HP/UX for its cluster capabilities. You have no technical reason at all, you even admit it's based on nothing but ideology. My god, I hope to never hire people like you.

    And BTW, Darwin is open source.

    --
  • jeez, i used to be just like you. then i realized how nice a GUI file manager was for discontinuous operations, and how the two worlds desperately need to meet.

    scenario: I just got a whole bunch of new pages for a publication submitted from an author I'm soliciting work from for a book I'm publishing. This author is a complete wiz with the publishing app, and also submits templates for me to use for the book as a whole. So my secretary got his new chapters and templates, copied the whole shebang into the source folder and cvs committed it. I cvs update my copy, now one of his templates has a typo, whups it screwed up someone else's chapter. Or maybe it was my last change to the templates that screwed things up ... so I need to search through the logs for files that were updated recently. Now I have a list of them in front of me. One by one I can click on them and review their history ... that change looks dubious, let's look at it in an editor. Okay, that's fine, next one. Whups, that one's messed, better revert it. Ok, next one. Whoah, I have no idea what that macro is, is that something from a new version? Todd would know, better mail it off to him ... send-to ... todd ... add a comment ... done.

    I just did several different operations on a list of files that would have scrolled off my screen long ago on a CLI, or I would have had to open a new term and copy and paste into other command lines to do so. Yes, perhaps you could train me on new ways, new scripts, new tools to do things solely with the command line, but what I just did feels natural to me. There are some tasks I wouldn't dream of using the GUI for, and a great many tasks I am just too reluctant to use the CLI for.

    --
  • I might also note that Jean-Louis Gasse was the Director of Marketing for Apple. He helped to make Apple the powerhouse it was in the early and mid-90's.

    --
  • By scrytch:
    I might also note that Jean-Louis Gasse was the Director of Marketing for Apple. He helped to make Apple the powerhouse it was in the early and mid-90's.

    Yup - and he was head of Apple France before that. Unfortunately when he came to Cupertino there were, er, "cultural differences" (let's just say he doesn't get a lot of Holiday cards from his peers back then...)

    Anyway, after that he jumped ship, took a bunch of Apple engineering talent with him & set out to pull a Steve Jobs (reinvent the Mac-but-it's-not-a-Mac-we-swear.) Unfortunately as we've seen big-time success has eluded him though he has managed to hang in there.

    What direct effect he had on Apple Marketing I don't know but those were the days when Power Computing was blowing the pants off of Apple in marketing.

  • Not a good argument. SGI was forced to abandon their GL interface because of insistance that they be compatable with X (GL is related to OpenGL but had calls for fonts, windows, and events, and arguably was better, and certainly easier to program, than X. Whole 2-D interfaces with buttons and text fields were written using GL, and were quite fast on 10 Mhz machines, which shows that powerful graphics primitives are NOT slow).

    They also had to give up on NeWS, they were the biggest user of NeWS other than Sun, and in fact used it far better and cleanly merged GL into it.

  • However, BeOS isn't POSIX certified. While BeOS does have hooks in it (from the software's point of view) to be multi-user, it always has one user. If you look at the file permissions and all that, there is a user called "Baron" and a user group. However, they don't really have any effect other than allowing POSIX software (such as CVS, which reads the username) to function properly. The OS itself isn't multi-user, it justs pretends that it is for POSIX software. However, there was some talk about making it multi user, and the API is already ready for it (for example the find_directory call has constants for the particular user folders and common folders) but it would be a lot of work, and I don't really see a benifet right now.
  • Of course you can. BeOS has an X server. And then there is VNC and a BeOS-native program [bebits.com] as well.
  • I was talking about the tests from 0.9-4, before Linux's Detonator 3 drivers. However, Linux DOES still lose in hi-res tests, but a good margin sometimes. For example, 37fps in 16x12 is marginal, while 46 is quite playable. However, its a moot point. Even at 640x480, Linux is SLOWER than Windows. That's simply should not be the case. (Especially since NT4 has even faster OpenGL performance than Win2K)
  • A) How is it not the point? You said BeOS couldn't do remote display, I pointed out that it could.

    B) Who cares if those capabilities are native? Technically, Linux doesn't natively have a GUI. Does that make Linux GUI's any less good?
  • Well, on my box I read email, prepare presentations, run a spreadsheet, browse the web, do the occasionial web-page or play a game, code something small & useful once in a blue moon.

    Along the way I need to get at files on a variety of servers (primarily AIX, NT, & Netware), interact in some constructive way with an Exchange server (IMAP & vCal are fine), print to a variety of network printers and be a good corporate network node. Synching with my Palm would also be nice.

    My biggest criteria for an OS & applications is compatibility - I need to be able to exchange standard business file-formats (read: MS Office)

    • flawlessly
    with others. I can't ask them to make special provisions for me - I need to be able to read & write in the lingua franca of the commerce world.

    So - can you do those on your Be? I mean, this is all well & great if you're living in a box somewhere but for those of us who are working all day with others how does Be hold up? I'm not being rhetorical - I honestly don't know & am curious. A few years ago when co-workers had it they eventually dropped it but perhaps things have changed since then.

"One day I woke up and discovered that I was in love with tripe." -- Tom Anderson

Working...