Slashdot Mirror


What is Open Source?

s390 writes "The Inquirer is running an article by Olliance about "What is Open Source?" It appears to be the first of a two-part series for managers about how to engage with the open source community. The writers seem to know their material. Are they on target or have they missed something important? Do PHBs really need to read this sort of introduction to get comfortable with the idea of using Linux and other open source software?"

322 comments

  1. Open Source Is by pnix · · Score: 0, Redundant

    Awesome. A life saver. Heck, it's even good!

  2. The thing I see is by BoomerSooner · · Score: 4, Interesting

    everyone seems to think just because something is Open Source it is default GPL'ed.

    Antitrust kind of fell into this trap (worst computer movie ever!).

    1. Re:The thing I see is by cK-Gunslinger · · Score: 1, Funny
      Antitrust kind of fell into this trap (worst computer movie ever!).
      You obviously were fortunate enough to miss "The Net."
    2. Re:The thing I see is by hpulley · · Score: 1
      If all reporters were engineers, I think news would be less slanted and more factually-based. But, most people are ignorant about the world around them, so there's no need to have the facts right.

      We can't all be domain experts. Articles on all sorts of subjects are poorly written due to lack of domain knowledge and research on the reporter's part. We notice the computer domain errors in print and movies because we work in this area but I'm sure surgeons, biologists and other experts groan at articles which we accept due to ignorance on our own part.

      The lack of any research ability is the sad part about all these reporters as I always thought this would be a key skill for a journalist but getting a weak article submitted early (first post, anyone?) seems more important than doing it right. Hey, maybe software engineers should be journalists after all, we could release articles early and then release service packs and patches later... its not a retraction, its a feature.

      --
      $#!^ happens, but why does it always have to happen to me???
    3. Re:The thing I see is by CableModemSniper · · Score: 2, Informative

      well in this particular article they mention BSD as well, maybe some others I don't recall. But they definitely didn't say everything was GPL.

      --
      Why not fork?
    4. Re:The thing I see is by deadsaijinx* · · Score: 1

      well, GPL, being the most prevalent license for OSS, has become nearly synonimous with Open Source for non-technical people. And is that really so bad? If you get the gist of the GPL, then you get the gist of Open Source. The only people whom the license would make any difference to are more skilled in the technical regions and more than likely know the difference between OpenS and GPL. just mho though

      --
      YOU SUCK BALLS!
    5. Re:The thing I see is by Quill_28 · · Score: 1

      Heck yah it's bad.

      If those people actually ever read the GPL license and the politics behind it, they will come to believe that all open source feels this way.

      IMHO that wouldn't be a good thing.

    6. Re:The thing I see is by pHDNgell · · Score: 1

      well, GPL, being the most prevalent license for OSS, has become nearly synonimous with Open Source for non-technical people. And is that really so bad?

      Yes, it really is that bad. Although you may believe in the ``copyleft'' type restrictions put forth by the GPL, it doesn't fit into a lot of business plans. If people who make those decisions believe that all open source works that way, they're likely to categorically overlook it.

      --
      -- The world is watching America, and America is watching TV.
    7. Re:The thing I see is by Anonymous Coward · · Score: 0

      The GPL may be OSI approved, but it is not an Open Source license!

      It is a Free Software license.

    8. Re:The thing I see is by mpe · · Score: 1

      well, GPL, being the most prevalent license for OSS, has become nearly synonimous with Open Source for non-technical people.

      In the same way that the original article uses "commercial" as a synonym for "proprietary"...

    9. Re:The thing I see is by mpe · · Score: 1

      Although you may believe in the ``copyleft'' type restrictions put forth by the GPL, it doesn't fit into a lot of business plans.

      Where do you get "many" from the conditions of the GPL are utterly irrelevent to any business which does not distribute software. Which is the vast majority. And of some relevence to companies which write software for contract.
      The only kind of busines Open Source dosn't fit is a business which licences proprietary software. Which is a small portion of a small portion of business plans.

    10. Re:The thing I see is by Ironica · · Score: 1

      Where do you get "many" from the conditions of the GPL are utterly irrelevent to any business which does not distribute software. Which is the vast majority. And of some relevence to companies which write software for contract.

      Regardless of whether it would actually ever come into play, businesses who are hung up on trade secrets and proprietary information will balk at the terms of the GPL, because they're not sure *what* it will oblige them to release (remember, lots of people don't actually know what "source code" is... and this article doesn't explain it, either).

      --
      Don't you wish your girlfriend was a geek like me?
    11. Re:The thing I see is by pHDNgell · · Score: 1

      I produce software that is used internally only. However, our software has been getting pretty good, and there's been a lot of talk selling our software in addition to our service. If your software licensing cannot survive a change in business plans, it's something to consider.

      --
      -- The world is watching America, and America is watching TV.
    12. Re:The thing I see is by mpe · · Score: 1

      Regardless of whether it would actually ever come into play, businesses who are hung up on trade secrets and proprietary information will balk at the terms of the GPL, because they're not sure *what* it will oblige them to release (remember, lots of people don't actually know what "source code" is... and this article doesn't explain it, either).

      What's really needed, IMHO, is an article which explains software licences. Including the difference between an ELUA and a copyright material distribution licence. As well as the consequences of using them. Some proprietary licences can be very nasty in obliging users to disclose confidential information.

  3. Maybe by T40+Dude · · Score: 5, Funny

    they should ask SCO ?

  4. Unfortunately.. by cK-Gunslinger · · Score: 5, Funny


    .. no one can be told what Open Source is.

    1. Re:Unfortunately.. by SkewlD00d · · Score: 0, Flamebait

      What, like the Matrix? Or, is it some big secret? Geez... you're starting to sound like a Scientologist. ;)

      --
      The biggest trick the devil pulled was letting lawyers become politicians so they can write the laws.
    2. Re:Unfortunately.. by cK-Gunslinger · · Score: 1

      Yeah, like the Matrix. I tell you that you can't be told what Open Source is, but 10 minutes later proceed to do exactly that.

    3. Re:Unfortunately.. by roman_mir · · Score: 4, Funny

      Oh, you mean we need to pop some pills and find out for ourselves?

    4. Re:Unfortunately.. by Anonymous Coward · · Score: 0

      Damn straight. Let's mee up here. I think that's gotta be the best place.

    5. Re:Unfortunately.. by SkewlD00d · · Score: 1

      Is there a blue and red pill interface? Or do I have to eat a monitor displaying the Aqua UI?

      Btw, there outta be a rule that open source/free/GPL'd projects must reuse as much code as possible from other projects, that way some embedded db doesn't use linear searches and insertion sort.

      --
      The biggest trick the devil pulled was letting lawyers become politicians so they can write the laws.
    6. Re:Unfortunately.. by smilingirl · · Score: 3, Funny

      Open Sores? Yuck! reference to Fox Trot comic: http://smilingirl31.tripod.com/comics/foxtrotlinux .gif

      --
      The Present is the point at which time touches eternity. - C.S. Lewis
    7. Re:Unfortunately.. by Miriku+chan · · Score: 1

      (it's bad to reply to sig's, etc etc etc) it's Stanislaw, with a 'w'. there isnt a 'v' in the polish alphabet /me is a pedantic pole.

      --
      shaolin punk, activist post-industrial
    8. Re:Unfortunately.. by roman_mir · · Score: 1

      Really? Well let me put it this way, I am translating his name from Russian (cyrillic) into Latin letters.

    9. Re:Unfortunately.. by MxTxL · · Score: 4, Funny

      This is your last chance. After this there is no turning back. You take the blue pill, the story ends, you wake up in your Windows environment and believe whatever you want to believe. You take the red pill, you stay in Wonderland, and I show you how deep Open Source goes... Remember, all I'm offering is the truth, nothing more...

    10. Re:Unfortunately.. by Anonymous Coward · · Score: 0
    11. Re:Unfortunately.. by UserGoogol · · Score: 1

      For reference, Open Source was the creation of Xenu. You see, there were two many software owners in the universe, so Xenu dropped all the software into a volcano for some reason, and they became Open Source.

      --
      "Never attribute to malice that which can be adequately explained by stupidity." -- Hanlon's Razor
    12. Re:Unfortunately.. by Anonymous Coward · · Score: 0
      That's funny. If you're such a diehard fan, you'd realize that he's POLISH !

      Teh calibre of /. posters never ceases to amaze.

    13. Re:Unfortunately.. by roman_mir · · Score: 1

      Yes, I know that, but I read him in RUSSIAN!

    14. Re:Unfortunately.. by SkewlD00d · · Score: 1

      Maybe Xenu didn't pay up there SCO license for 1st amendment rights? I mean who likes/is a Scitlglts anyhow? They aren't a religion, and I just use them as a comparison to patent whores and black-box, monolithic engineering. I'm not saying that you have to be a red-book-toting Communist to support OSS/GNU/GPL, it's just ironical the sort of fanaticism involved in platform/editor/political flame wars. I wonder what would happen if the gov't mandated that all software should go free, non-commercial open source (w/ some NDA blah blah EULA crap) after 10 years. Then we would be able to laugh at all the bugs in Windoze using some nifty code-coverage/CASE tools. ;)

      --
      The biggest trick the devil pulled was letting lawyers become politicians so they can write the laws.
    15. Re:Unfortunately.. by nite_warrior · · Score: 1

      I told you, I can only show you the door, you will have to go throuh it

    16. Re:Unfortunately.. by arose · · Score: 1

      Aqua is the blue pill.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    17. Re:Unfortunately.. by tcak · · Score: 1

      Whoa!

    18. Re:Unfortunately.. by Anonymous Coward · · Score: 0

      If I told you, I would have to kill you.

  5. What Yoda would say? by maizena · · Score: 0, Funny

    "May The Source Be With You..."

  6. This is what it is by SkewlD00d · · Score: 2

    Enough said. theRegister: RTFM!! Must be a slow news day.

    --
    The biggest trick the devil pulled was letting lawyers become politicians so they can write the laws.
    1. Re:This is what it is by Anonymous Coward · · Score: 0

      Thats what it is for a tiny number of geeks.

      For management-people in big companies (and small too) it's just about free labour, it's nice not having to pay for stuff.

      If anyone thinks anything else you are just fooling yourself.

    2. Re:This is what it is by SkewlD00d · · Score: 0, Troll

      Haha... something for nothing, eh? That's called "free as in free-beer" software, i mean *BSD license. ;)

      --
      The biggest trick the devil pulled was letting lawyers become politicians so they can write the laws.
    3. Re:This is what it is by Anonymous Coward · · Score: 0

      No one pays for GPL'd software either.

    4. Re:This is what it is by Anonymous Coward · · Score: 0

      Haha... something for nothing, eh? That's called "free as in free-beer" software, i mean *BSD license. ;)

      Sure, but the "something for nothing" is what the PHBs will care about - they won't care about the beer / speech distinction.

    5. Re:This is what it is by antis0c · · Score: 3, Informative

      Funny, seeing as Free Software and Open Source are two entirely different things. They each have their own foundations. The Free Software Foundation, and the Open Source Initiative.

      FSF, GNU, GPL and all that was started by Richard Stallman, RMS from here on. Open Source, OSI and the Open Source Definition was first drafted by Bruce Perens. They are very similar in nature but have a lot of differences in the details. There FSF focuses primarily on GNU GPL and LGPL, The OSI and OSD are more broad, and do include the GPL under its terms, but also a variety of other licenses. The OSD sets up a moral standard, with 10 (originally 9) Sections to define a set of common guidelines a license must have to be considered Open Source.

      The philosphies of these two men differ slightly. Where as RMS believes ALL software should be free and no commercial software should exist, Bruce Perens believes both can co-exist and co-mingle for the greater benefit of both. If you've ever seen the movie Revolution OS, they talk a good amount about the differences between FSF and OSI and GPL and OSD. Bruce Perens is even quoted as saying that the major difference is RMS believes all software should be GPL, and anything that isn't hurts the GPL. RMS doesn't seem such a 'great leader' after you get into the details. Granted, he's done a lot of good things, I hear the non-jews had a good life in Nazi Germany too.

      So, yes, RTFM indeed.

      --

      ..There's a-dooin's a-transpirin'
    6. Re:This is what it is by ichimunki · · Score: 1

      Wow. Nice troll. Nazi Germany. You almost had me, too.

      --
      I do not have a signature
  7. Like it or not, managers default to commercial by Sheetrock · · Score: 5, Insightful
    Which means that Open Source needs to be carefully pitched to them -- commercial, closed source software is how business has been done for thirty years, while free software is still kind of a wierd new hippiesh thing (although having big-time companies like IBM embracing it helps.)

    It's like the saying goes; when all you have is a hammer, everything looks like it needs a pounding. Nobody ever got fired buying Microsoft, whereas Open Source seems like a gamble... even moreso now with the bogus SCO lawsuit. Calmly and rationally explaining to the people that make the procurement decisions at your company that free software is a valid alternative and explaining why is necessary, because by default they're going to want to go with what they've always went with.

    --

    Try not. Do or do not, there is no try.
    -- Dr. Spock, stardate 2822-3.




    1. Re:Like it or not, managers default to commercial by Anonymous Coward · · Score: 0

      IBM's employess dropped the Blue Suits and Ties for Sandals and Dreddies?

    2. Re:Like it or not, managers default to commercial by bogado · · Score: 1

      I think big business, care mutch about the warranty (even if the EULA say the program is guaranteed to do nothing) and support (+2 hours of phone menus) then anything else. That is why we need big companies to suport and warranty linux, like IBM and redhat. Small business and home offices should be more confortable with using linux, if they had a little push like those reviews and introductions arround.

      --
      []'s Victor Bogado da Silva Lins

      ^[:wq

    3. Re:Like it or not, managers default to commercial by brejc8 · · Score: 4, Interesting

      A friend of mine who works at an unnamed Swedish company was very much for open source software, but when his managers were thinking of buying software they allways went for the medium-small sized companies reather than the large sized or open-source. The reason was that if they programs didn't work purfectly they could put pressure for the companies to fix it. If they refused they would bury them in legal threats and colapse the company and move on. Thus not many companies would refuse to fix bugs and solve problems.
      Interestingly the concept of the company fixing its own problems as they hold the source was just unthinkable. No manager would give themselves more work no matter how much money it would save.

    4. Re:Like it or not, managers default to commercial by Anonymous Coward · · Score: 0

      Right On!

      Businesses are resistant to change, and always have been. Change is an unknown, and the unknown is scary. Would a company rather have a constant 5% growth, or a varying growth of 1 to 10%? They'd take the 5% any day, as it's a much better buy for investors/stockholders.

      I say hoorah! for any business even looking at OSS of any sort, even if they don't use it. Why? Because that assessment may open the doors for applications which are more suitable for OSS programs.

    5. Re:Like it or not, managers default to commercial by Realistic_Dragon · · Score: 1

      Big business does not get support direct from the vendor except in rare cases.

      I know of one company that contracts IT to CSC, at £1200+/box/yr plus £40/call plus £80/relocation. (IE moving the box accross the room or accross the world.)

      They think it's worth it because it gives them known costs, support who know the business (although that bit backfires a bit...), someone to blame when things go wrong (penalty clauses and SLAs) and all the other things that make them comfortable.

      They couldn't give a rats ass as if Linux or Windows was deployed, as long as it brought their cost base down. It's CSC who choose not to do it, not the company in question.

      (FWIW the numbers there probably sounded like a good deal 5+ years ago when the 10 yr contract was signed. Bet someone feels a bit foolish now.)

      --
      Beep beep.
    6. Re:Like it or not, managers default to commercial by cnkeller · · Score: 3, Interesting
      The reason was that if they programs didn't work purfectly they could put pressure for the companies to fix it. If they refused they would bury them in legal threats and colapse the company and move on.

      I find that kind of interesting, if not slimy. Most software includes some type of "provided as-is license". This would seem to indicate that a customer doesn't have a lot of legal ground to stand on regarding buggy software. Custom contract work is probably a different story.

      Has anyone actually sued (and won) a vendor for buggy software? I'd be interested because Quicken on the Mac, though far more useful than Gnucash, crashes quite often. Intuit has acknowledged this, but provided no fix. Guess they think I should be grateful they didn't write info to my MBR....

      --

      there are no stupid questions, but there are a lot of inquisitive idiots

    7. Re:Like it or not, managers default to commercial by dsr9996 · · Score: 4, Interesting
      My experience at the company I work for has verified what your friend's Swedish company does. Big companies are going to be unresponsive to bug reports and feature requests because big companies by nature move slowly, are ponderous, and not as nimble as smaller ones. The same, interestingly, is also true of groups within companies.

      The only reason big companies will be responsive to requests is if the company doing the requesting is also big (i.e. a very important client). This makes perfect business sense: It is much more important to make sure a client that spends $10 million on your products each year is happy versus a researcher at a university that spends $1 thousand.

      Your other point about companies fixing bugs in OSS since they have access to the code is also right on. It is not always easy to fix bugs in code, especially if the code is non-trivial in size or complexity. It takes time to learn the code well-enough to solve bugs in it, unless they are glaringly obvious. So the time that may be saved by reusing open source code must be weighed against the time it takes to learn that code if a company intends to make fixes to it.

      Finally, I think most companies do not understand open source licenses, and because of this ignorance, they are afraid that by using open source code they will have to give away all their proprietary code. The threat of this alone is enough to make any company afraid.

      At the company I work at, open source proponents would need to convince the high ups at the company (CEO, CIO, etc.) about the safety and utility of open source, and once those guys made a decision to use it, they would make it a possibility for group managers and individual developers to explore open source solutions to use in their projects.

      Peaceful regards,
      Devin

    8. Re:Like it or not, managers default to commercial by Cereal+Box · · Score: 4, Insightful

      Interestingly the concept of the company fixing its own problems as they hold the source was just unthinkable. No manager would give themselves more work no matter how much money it would save.

      See, you have the misconception that simply having access to the source means you can fix problems in an acceptable amount of time. If you've ever had to pore over a massive project you'll realize that you could spend a couple days trying to track down and fix a problem that is preventing you from finishing your real work or you could simply send a problem description off to the guys who originally wrote the code (and who you're already paying for), and they'll probably be able to fix the problem far quicker than you ever could. THAT is the reason closed-source software is so appealing. If you have a problem with a piece of code you bought you can tell them "hey, I've got a problem, I'm paying you, get on this problem and fix it for me ASAP or we'll be re-evaluating our business relationship with you." With open source software, you might get lucky with helpful developers and you might not. You never know. What you do know is that you don't have the ability to really push open source developers to fix problems for you, and that's a major drawback.

    9. Re:Like it or not, managers default to commercial by Jason+Earl · · Score: 2, Insightful

      If you want to be able to put pressure on Free Software developers, then you have to have a business relationship with them. This is no different than what happens with commercial software vendors. For example, let's say you purchase a software package, and then decide that you are going to skip an expensive upgrade cycle. With commercial vendors the most likely response to "fix this problem, or else" is "it's fixed in the next version that will be $XXX to upgrade your licenses."

      With Free Software you might get your problem solved for free. I personally have had very good luck bringing up issues with Free Software. However, if you are truly worried about support, the simple answer is to purchase a support contract from the vendor of your choice. Not only will your support contract likely cost you less than licensing commercial software, but if you feel your vendor isn't giving you adequate support you can purchase support from someone else.

      In short, if you pay the Free Software developers money, then you can threaten to change your business arrangement in the future. If you don't, then practice up on your diplomacy because you are going to have to sweet talk developers into helping you.

    10. Re:Like it or not, managers default to commercial by Cereal+Box · · Score: 1

      However, if you are truly worried about support, the simple answer is to purchase a support contract from the vendor of your choice. Not only will your support contract likely cost you less than licensing commercial software, but if you feel your vendor isn't giving you adequate support you can purchase support from someone else.

      You're saying that you can buy a support contract from any number of organizations? Forgive me for sounding less than enthusiastic about that prospect. If I buy support for product X from company Y, yeah they're my only option, but they make product X and the guys who coded it are intimately familiar with it. They have specialized knowledge of it.

      Now let's say I want support for Apache. Who do I buy that from (honest question, I don't know who you can "pay" to support Apache, or any arbitrary open source program)? How am I supposed to expect them to have intimate knowledge of the product? It sounds to me like buying "open source support" from a company means you're paying these guys to be "jacks of all trades", which of course means that they are "masters of none". Doesn't sound like such a good deal to me.

    11. Re:Like it or not, managers default to commercial by Aadain2001 · · Score: 2, Insightful

      The Open Source option is just that, an option. It is not the end-all, be-all of software paths for a company to follow. But it should still be looked at and given a chance. The people who can benifit from Open Source the most are large companies who already have programers on staff. The programers can learn the project and start fixing bugs/adding features to it without the need to deal with all the corporate politics that are involved with B2B. This way you can put pressure on a person to get the job done since they are inhouse. And, in the case of licenses like the GPL, the company doesn't have to give the work back if they only use it internally. But they could offer the fixes/features back to the world and see if others would add features/fixes to it as well, which they could merge back into the internal version. Think of it as getting a large pool of free eyes to look at what you are already doing and paying for.

      --
      Space for rent, inquire within
    12. Re:Like it or not, managers default to commercial by MrResistor · · Score: 2, Insightful

      See, you have the misconception that simply having access to the source means you can fix problems in an acceptable amount of time. If you've ever had to pore over a massive project you'll realize that you could spend a couple days trying to track down and fix a problem that is preventing you from finishing your real work or you could simply send a problem description off to the guys who originally wrote the code (and who you're already paying for), and they'll probably be able to fix the problem far quicker than you ever could. THAT is the reason closed-source software is so appealing. If you have a problem with a piece of code you bought you can tell them "hey, I've got a problem, I'm paying you, get on this problem and fix it for me ASAP or we'll be re-evaluating our business relationship with you." With open source software, you might get lucky with helpful developers and you might not. You never know. What you do know is that you don't have the ability to really push open source developers to fix problems for you, and that's a major drawback.

      Going to the maintainer or a major developer for the project and saying "hey, I have this problem and will pay you $x to fix it" would probably be plenty of leverage on an OS project, and would probably still be cheaper than the CS solution, and likely eliminates the need to be an asshole about it.

      You catch more flies with honey than with vinegar.

      Basically, what you're saying is that CS is a more attractive solution than OS for people who have no vision and no people skills.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    13. Re:Like it or not, managers default to commercial by Dalcius · · Score: 2, Insightful

      "you could spend a couple days trying to track down and fix a problem that is preventing you from finishing your real work or you could simply send a problem description off to the guys who originally wrote the code (and who you're already paying for), and they'll probably be able to fix the problem far quicker than you ever could."

      This point does have merit, but I suppose you're talking about problems with small to mid sized companies. Big ones (Like Microsoft, IBM, Novell, etc.) aren't going to fix your problems any time soon; they have so many customers, unless you're a big-shot (who can spend the $$$ to fix it yourself), they won't care. Have you had the pleasure of paying money for an incident to report a bug to MS? :)

      ---
      "What you do know is that you don't have the ability to really push open source developers to fix problems for you, and that's a major drawback."

      No, but truth be told, most OSS developers aren't working on their projects because they're told to or are being paid. They do it because their projects are their babies.

      Typically, problems reported are fixed in relatively short order because:
      1) you've likely, in the process of debugging your own software or tools, have isolated the problem to a specific area and pattern and
      2) OSS folks almost always use the software they write themselves. That's usually why they write it in the first place.

      Your argument has some weight, but I don't think it pans out in the large scheme of things.

      [Apple Switch] My name is Dalcius, and I'm a Software Analyst (debugger) for a mid-sized company that deals with semi-large ones. [/Apple Switch]

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    14. Re:Like it or not, managers default to commercial by swv3752 · · Score: 1

      You would buy from Red Hat or Mandrake or SuSE.

      Most Distros sponsor or employ a developer for most of the large projects. One can also contract directly with the developers.

      --
      Just a Tuna in the Sea of Life
    15. Re:Like it or not, managers default to commercial by Cereal+Box · · Score: 1

      Going to the maintainer or a major developer for the project and saying "hey, I have this problem and will pay you $x to fix it" would probably be plenty of leverage on an OS project, and would probably still be cheaper than the CS solution, and likely eliminates the need to be an asshole about it.

      You catch more flies with honey than with vinegar.


      The "fix the damn thing" attitude is not meant to be taken literally. Project members don't speak to other project members like that. However, to the group whose services you're paying for, it is certainly weighing on their mind that sub-par performance will not result in renewed contracts in the future.

    16. Re:Like it or not, managers default to commercial by Cereal+Box · · Score: 1

      Employ "a" developer for "most" of the large projects? Buddy, if you're buying support for a software package you want the whole team at your disposal. After all, the money you're paying go towards ensuring that the development team as a whole is responsive to your needs, not just one guy.

    17. Re:Like it or not, managers default to commercial by Cereal+Box · · Score: 1

      This point does have merit, but I suppose you're talking about problems with small to mid sized companies. Big ones (Like Microsoft, IBM, Novell, etc.) aren't going to fix your problems any time soon; they have so many customers, unless you're a big-shot (who can spend the $$$ to fix it yourself), they won't care. Have you had the pleasure of paying money for an incident to report a bug to MS? :)

      You're probably not familiar with how this normally works. If you license a product from IBM or MS it's not like all your communications go from the very top down to the bottom and they simply dump a product on your lap and leave you alone. You are generally (always?) given a contact with the team lead(s) and have a way to contact the people who coded the software itself. To say that licensing from a big corporation means your concerns won't be heard unless you are also a big corporation is pretty much dead wrong.

      No, but truth be told, most OSS developers aren't working on their projects because they're told to or are being paid. They do it because their projects are their babies.

      Typically, problems reported are fixed in relatively short order because:
      1) you've likely, in the process of debugging your own software or tools, have isolated the problem to a specific area and pattern and
      2) OSS folks almost always use the software they write themselves. That's usually why they write it in the first place.


      Again, open source developers don't have a business relationship with you, so they don't have any real incentive to be attentive to your needs. They don't have to fix anything. There are many developers who may just flat out refuse to alter the way their program works, even if it's minor thing, because "it's their baby".

      We're working with software from a big company and we've requested numerous times for changes in the behavior of their software that would allow it to better integrate with our software. You know what? They've been very receptive to it and have always gotten back to us concerning problems very quickly. Hell, we've even sent them changes we've made to their code at times. Sure, they don't have to let us do any of that, but then again, we don't have to continue to pay them either. That gives them incentive to provide the best service they can. With open source, you don't necessarily get that.

    18. Re:Like it or not, managers default to commercial by Drakonian · · Score: 1
      Basically, what you're saying is that CS is a more attractive solution than OS for people who have no vision and no people skills.

      Hehe, I realize you were talking about customers but in terms of OSS developers, that statement is hilarious!

      --
      Random is the New Order.
    19. Re:Like it or not, managers default to commercial by Jason+Earl · · Score: 2, Insightful

      You're saying that you can buy a support contract from any number of organizations? Forgive me for sounding less than enthusiastic about that prospect. If I buy support for product X from company Y, yeah they're my only option, but they make product X and the guys who coded it are intimately familiar with it. They have specialized knowledge of it.

      It's no different in the Free Software world. Free Software doesn't spring forth from the mind of Zeus fully grown, some hacker writes it. Most of these hackers have mortgages and such just like the rest of us.

      Now let's say I want support for Apache. Who do I buy that from (honest question, I don't know who you can "pay" to support Apache, or any arbitrary open source program)? How am I supposed to expect them to have intimate knowledge of the product? It sounds to me like buying "open source support" from a company means you're paying these guys to be "jacks of all trades", which of course means that they are "masters of none". Doesn't sound like such a good deal to me.

      Apache support is easy because you can get it from almost anywhere. For example, both IBM and RedHat have engineers that are part of the core Apache group, but just about any major organization has people that are well versed in Apache. Chances are good with Apache that you will have a configuration issue and not an actual bug.

      A much better example, is PostgreSQL support. First of all, PostgreSQL is quite a bit more complex than a simple http server. Secondly, PostgreSQL is a project that I personally am more familiar with. You can get support from PostgreSQL Inc. or Command Prompt command, and RedHat will sell you support for their Red Hat Database which is nothing more than rebranded PostgreSQL. All of these organizations have staff members that are extremely familiar with PostgreSQL.

      From my own personal experience these smaller Free Software support organizations are a world apart from the heavily scripted phone support available from most commercial software development firms. Heck, all of us have been on hold for an eternity only to have the tech ask us if we have rebooted the server. Just like anything else it generally boils down to how difficult your problem is, and how much you are willing to pay to make it go away. If you offer RedHat enough money they will put Tom Lane on your PostgreSQL problem around the clock and the problem will simply go away. Try doing that with Oracle or MS SQL Server.

    20. Re:Like it or not, managers default to commercial by Dalcius · · Score: 1

      "You're probably not familiar with how this normally works. If you license a product from IBM or MS it's not like all your communications go from the very top down to the bottom and they simply dump a product on your lap and leave you alone. You are generally (always?) given a contact with the team lead(s) and have a way to contact the people who coded the software itself. To say that licensing from a big corporation means your concerns won't be heard unless you are also a big corporation is pretty much dead wrong."

      If this is the case, then I stand corrected. Somehow, though, from what I've heard from folks I work with, the things I've seen personally and the things I read about online (in dar intarnet huh huh), companies like MS generally aren't inclinded to fix problems.

      ---
      "Again, open source developers don't have a business relationship with you, so they don't have any real incentive to be attentive to your needs. They don't have to fix anything."

      As someone else suggested, throw them some money to fix a bug. Many OSS developers get cash this way. It will almost certainly be cheaper to throw him some cash than to fix it yourself, and will likely be about as expensive as an "incident report" or yearly support contract. ;)

      ---
      "There are many developers who may just flat out refuse to alter the way their program works, even if it's minor thing, because "it's their baby"."

      How many medium to large corporations have you known of to alter their software at a single customer's request? This practice is generally frowned upon in all but the smallest companies, unless, of course, the company is in the business of selling solutions, which most medium-larged sized companies aren't.

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    21. Re:Like it or not, managers default to commercial by 3Bees · · Score: 1

      I don't really see how your argument has anything to do with close-source vs. open-source, or even GPL vs. whatever. All you have argued is the merits of not handling source internally when you can just pay the programmers/maintainers to do it.

      --
      "I think we should tax people who stand in water! " - Mr. Gumby
    22. Re:Like it or not, managers default to commercial by tcopeland · · Score: 1

      > and they'll probably be able to fix
      > the problem far quicker than you ever could.

      Yup, they'll probably be able to fix it. But they won't fix it immediately. Instead, they'll say that's a "known issue" which should be solved by the next version, which will be out in a month. In the meantime, you can work around it by doing something clunky which you had figured out already.

      > or we'll be re-evaluating our
      > business relationship

      Any program that big and complex will have you tied down via its database schema/interface/licensing scheme/etc. "We'll switch to a competitor's product" will be an empty threat.

      "It's a massive project" is more a argument for than against open source.

    23. Re:Like it or not, managers default to commercial by poot_rootbeer · · Score: 2, Interesting


      I was going to point out that reliable, accountable support is available for many open-source software packages too, from vendors ranging from IBM and RedHat down to the self-employed geek down the street that runs his own consulting business, but I realized you had a point.

      When a commercial support organization for an open-source application gets a bug report, they can analyze the source code to gain an understanding of the app design, troubleshoot to the best of their understanding, and consult the original authors via mailing lists or whatever about the things they can't understand themselves (and the authors have no obligation to respond, since they're not getting paid to). If the support company does not provide good support, they lose the support contract.

      When the support org of a proprietary software company gets a bug report, they have vast amounts of internal resources available to help them understand, troubleshoot, and correct the error. Many of the people who originally developed the application are likely to still be employed by the company, obligating them to share what they know. If the software company does not provide good support, they lose the support contract -- AND lose out on future sales of their product.

      Ultimately, source code alone is NOT sufficient documentation to support an application. In order to understand how something works, you need the project specs, design docs, etc. -- and very few OSS projects provide that kind of documentation with their source. On the other hand, most commercial developers are required by company policy to create such documentation.

    24. Re:Like it or not, managers default to commercial by iabervon · · Score: 1

      Actually, managers in my experience default to widely-used, industry standard tools. It's just that these tend to be commercial. But there are plenty of commercial packages which managers will avoid by default, because they aren't what everyone else uses.

      There are a few open source packages (such as Apache) that are the industry standard in some segments, and it would be odd to use something else instead.

      If you're looking to get something where there's no established package at all (Java charting packages, for instance), a free package without license hassles where you can modify it yourself is generally preferred over a commercial one.

      (The SCO lawsuit is a contract lawsuit. SCO has a contract with MicroSoft. SCO, as Caldera, has actually gotten a settlement out of MicroSoft in the past. I'd hesitate to buy from such a vulnerable company at this point...)

    25. Re:Like it or not, managers default to commercial by Cereal+Box · · Score: 1

      Yup, they'll probably be able to fix it. But they won't fix it immediately. Instead, they'll say that's a "known issue" which should be solved by the next version, which will be out in a month. In the meantime, you can work around it by doing something clunky which you had figured out already.

      I see this misconception a lot from OSS advocates, this whole notion that the only support you'll get from commerical software is "wait until the next release". Either you work with very poor companies or you have no experience working in a professional environment. We rely on software from a large corporation and when we have a problem we talk to the team itself, and they have always been very prompt and responsive to our needs. It is not unheard of to get custom builds of another group's software that addresses your particular problem. If you have to settle for this "wait until the point release" crap, you're working with the wrong people.

    26. Re:Like it or not, managers default to commercial by tcopeland · · Score: 1

      > the only support you'll get from
      > commerical software

      Not "the only support", but, perchance, "many time the only support". Eschew absolutes!

      > you work with very poor companies

      Possibly.

      > you have no experience working
      > in a professional environment

      Could be. I'm a mere grasshopper!

      > they have always been very
      > prompt and responsive

      Excellent. A good situation, to be sure. Not the rule, though, I daresay.

      > It is not unheard of to get custom builds

      Nor is it unheard of to be deflected with a "wait until the next release".

      > you're working with the wrong people.

      Quite possible!

    27. Re:Like it or not, managers default to commercial by mabhatter654 · · Score: 1
      But this could show that OSS is good for the small contractor/ programming house!


      The manager has clout over the developers because they are only supporting probably under 100 customers! a $100k check is a big deal--and a meal. They are more willing to work with customers financially (take payments) and that gives some leverage to the customer to hold up the checks (after the first ones have cleared...) if things don't work as promised. It's a carrot-stick thing. [like if your software takes out the business before they finish paying you. that's incentive!] This is capitalism in it's truest form and at it's best!


      at the same time OSS would fit nicely in smaller shops development model. The OSS toolset is cheaper, the only "cost" being to return some of the code you patch. If spun properly it could even be a marketing tool. In most cases the "customers" aren't going to sell out your code--they weren't smart enough to write it in the first place...the CD would most likely end up at the bottom of a drawer somewhere. They're after the relationship with the vendor--they really want to pay somebody else to worry about the code....and again, some common sense applies because while the code is OSS, understanding their business' needs isn't something that can be "canned".


      After hanging out here for a while, that could be a good business to "can" OSS and sell the package deal to businesses using OSS. There's several people here that do it, if you're good and responsive there's got to be money in it. People are fed up with big business software for exactly this reason. [it's why I have a job! my boss doesn't want to just pay a mindless mega corp.]

    28. Re:Like it or not, managers default to commercial by wilhelm9 · · Score: 1
      This point does have merit, but I suppose you're talking about problems with small to mid sized companies. Big ones (Like Microsoft, IBM, Novell, etc.) aren't going to fix your problems any time soon; they have so many customers, unless you're a big-shot (who can spend the $$$ to fix it yourself), they won't care. Have you had the pleasure of paying money for an incident to report a bug to MS? :)
      Not that I have been involved with Microsoft support on a daily basis, but two of the three support cases I have worked with against Microsoft was actually fixed. Ok, the fixes wasn't released promptly but quick enough. In one case I got a "hotfix" within a few weeks that we could install at customer sites manually until the regular service pack was released. But I agree that the support organisation itself can be a major hurdle, but that is not a property that really has anything to do with whether the product is released with source or not. It is just that when software companies becomes larger, it becomes more difficult for support personnel to know everything about each product. Keeping development staff at support jobs is just wasting resources in a way that only smaller companies with limited number of clients can do.
      No, but truth be told, most OSS developers aren't working on their projects because they're told to or are being paid. They do it because their projects are their babies. Typically, problems reported are fixed in relatively short order because: 1) you've likely, in the process of debugging your own software or tools, have isolated the problem to a specific area and pattern and 2) OSS folks almost always use the software they write themselves. That's usually why they write it in the first place.
      There is *nothing* unique about this that makes these properties apply to open-source software only. I work developing a closed source product for a smaller company (80 employees) and I can tell you, most of the 15 of us actually coding the product both consider it our baby as well as we use it ourselves.
    29. Re:Like it or not, managers default to commercial by mpe · · Score: 1

      A friend of mine who works at an unnamed Swedish company was very much for open source software, but when his managers were thinking of buying software they allways went for the medium-small sized companies reather than the large sized or open-source. The reason was that if they programs didn't work purfectly they could put pressure for the companies to fix it. If they refused they would bury them in legal threats and colapse the company and move on. Thus not many companies would refuse to fix bugs and solve problems.
      Interestingly the concept of the company fixing its own problems as they hold the source was just unthinkable. No manager would give themselves more work no matter how much money it would save.


      Are lawyers (and legal firms) cheaper than programmers (and programming firms) in Sweden? This sounds like a variation on the "who do you sue" type FUD.

    30. Re:Like it or not, managers default to commercial by mpe · · Score: 1

      See, you have the misconception that simply having access to the source means you can fix problems in an acceptable amount of time. If you've ever had to pore over a massive project you'll realize that you could spend a couple days trying to track down and fix a problem that is preventing you from finishing your real work or you could simply send a problem description off to the guys who originally wrote the code (and who you're already paying for), and they'll probably be able to fix the problem far quicker than you ever could. THAT is the reason closed-source software is so appealing.

      Since you typically don't know who actually wrote the software with a proprietary program how do you know that they will be the people who will attempt to fix it.

      If you have a problem with a piece of code you bought you can tell them "hey, I've got a problem, I'm paying you, get on this problem and fix it for me ASAP or we'll be re-evaluating our business relationship with you."

      If you are paying someone to work on the code it really dosn't matter if the code itself is open source or proprietary. But if things do go wrong then with open source you can still go elsewhere, with proprietary software if the vendor won't fix it then you are out of luck.

      With open source software, you might get lucky with helpful developers and you might not. You never know. What you do know is that you don't have the ability to really push open source developers to fix problems for you, and that's a major drawback.

      If you want software to do something specific you pay someone to do it. Would you sit around hoping a proprietary software vendor will start selling something which does what you want it to do...

    31. Re:Like it or not, managers default to commercial by mpe · · Score: 1

      You're saying that you can buy a support contract from any number of organizations? Forgive me for sounding less than enthusiastic about that prospect. If I buy support for product X from company Y, yeah they're my only option, but they make product X and the guys who coded it are intimately familiar with it. They have specialized knowledge of it.

      How do you know company Y actually wrote product X? Maybe they actually bought it from company Z. Even if people at company Y did write it how do you know they are still working there?

    32. Re:Like it or not, managers default to commercial by mpe · · Score: 1

      Buddy, if you're buying support for a software package you want the whole team at your disposal. After all, the money you're paying go towards ensuring that the development team as a whole is responsive to your needs, not just one guy.

      In which case you'd need to deal with those people fairly directly. With a lot of proprietary software this is very difficult since the identity of the programmers can be just as secret as the source code.

    33. Re:Like it or not, managers default to commercial by mpe · · Score: 1

      Going to the maintainer or a major developer for the project and saying "hey, I have this problem and will pay you $x to fix it" would probably be plenty of leverage on an OS project, and would probably still be cheaper than the CS solution

      Possibly quicker too. Since there is plenty of software the CS option cannot touch.

    34. Re:Like it or not, managers default to commercial by mpe · · Score: 1

      When a commercial support organization for an open-source application gets a bug report, they can analyze the source code to gain an understanding of the app design, troubleshoot to the best of their understanding,

      With an open source product it's perfectly possible that their customer has given them more useful information than "XYZ dosn't do ABC". Since they have access to the code too.

    35. Re:Like it or not, managers default to commercial by Dalcius · · Score: 1

      1) I understand that many companies are on the ball; mine generally is. (Hopefully I should know, I'm one of the guys whose job it is to fix these problems!). However, the corporate attitude is to make money. I don't think anyone can argue with that. Many tech companies, software companies especially, are so concerned with the bottom line these days that fixing problems and keeping the customer smiling isn't a priority, since they can still sell their product. This is by no means applicable to all companies, but it is a large trend.

      2) Although you are correct in pointing out that developers in companies still have "their babies" and do use them, I think you're missing the overall point (which I didn't point out clearly). Companies are, again, after money. There are deadlines, there are insane managers who push for unrealistic release dates and then move on to new software instead of fixing what just went out the door. The vast majority of software companies do it for the money, whereas the vast majority of OSS developers do it for the fun and the personal benefit alone.

      Just because you do it for money doesn't mean you won't invest yourself in your work; when I was developing at my company just over a year ago, my projects were my passion. I put my all into them. But a corporate environment isn't a place where you often can take the time to do things right.

      --
      ~Dalcius
      Rome wasn't burnt in a day.
  8. Re:no by Anonymous Coward · · Score: 0

    Respect open source?

    Open source is about free (unpaid) labour, nothing else.

  9. I loved antitrust by zapp · · Score: 4, Insightful

    Antitrust beat the hell out of movies like Hackers and The Net.

    Atleast Antitrust used GNOME, real unix commands, etc... had hot girls, and an actual plot.

    Maybe it didn't portray the fineprint of the GPL, but it did pretty well (I thought) at showing how corrupt corporations can be.

    --
    no comment
    1. Re:I loved antitrust by xutopia · · Score: 4, Funny

      eveytime there was code on the screen it was funny as hell!

      If (byte byte)
      {
      byte byte byte
      Byte ** asdfasdf
      Byte byte is good for a byte()
      so byte byte byte
      }

    2. Re:I loved antitrust by Anonymous Coward · · Score: 1, Insightful

      Atleast Antitrust used GNOME, real unix commands, etc... had hot girls, and an actual plot.

      Yeah...and all the code was HTML. Sorry, but if you're going to make a movie based on computers and put so much detail into using proper software to make things look more authentic, the LEAST you can do is rip some GPL'd code from somewhere and use that. The geek factor in that alone would have boosted the movie a lot.

    3. Re:I loved antitrust by Kedanoth · · Score: 1
      Funniest part was seeing the (extreme) enthusiasm when Tim Robbins and Ryan Phillippe point out bits of code.

      "Look at this!" -Tim points to random switch statement- "That's excellent!"

    4. Re:I loved antitrust by Anonvmous+Coward · · Score: 1

      "Antitrust beat the hell out of movies like Hackers and The Net."

      Yeah, afterall any movie that illustrates Bill Gates being arrested and Microsoft going down the tubes is bound to be considered a 'good movie' here.

    5. Re:I loved antitrust by 222 · · Score: 1

      Takedown was much better, imho. Its a shame its only available via shady irc channels and perhaps kazaa.

    6. Re:I loved antitrust by Angry+Pixie · · Score: 1

      You're fooling yourself. PCI and 16 million colors will change everything ;)

    7. Re:I loved antitrust by Angry+Pixie · · Score: 1

      Early Raul Julia flick, Overdrawn at the Memory Bank - best hacking flick ever, and this is coming from a MST3K devotee ;)

    8. Re:I loved antitrust by Dan+D. · · Score: 1

      You are in so much trouble now. Don't you realize that code you just published was under NDA? You've got no respect for IP, pirate!

      --
      People who quote themselves bug the crap out of me -- Me.
    9. Re:I loved antitrust by daeley · · Score: 1

      Antitrust beat the hell out of movies like Hackers and The Net.

      Sorry, any movie with Sandra Bullock in a bikini typing on a laptop at the beach might qualify as Best Computer Movie Ever. ;)

      --
      I watched C-beams glitter in the dark near the Tannhauser gate.
    10. Re:I loved antitrust by rsmith-mac · · Score: 1

      Actually, in the DVD version, one of the extras mentioned that they used real GPL code in scenes where they showed code. So unless someone wasn't telling the truth on their end, you wouldn't have been seeing something like that in the movie.

    11. Re:I loved antitrust by hitchhacker · · Score: 1

      I think that was code for something like an HTTP server.
      like:

      if(msg[0] == 'G' && msg[1] == 'E' && msg[2] == 'T')

      faster than calling strcmp(msg, "GET")

      -metric

    12. Re:I loved antitrust by Anonymous Coward · · Score: 0

      Sandra Bullock is butt ugly. You need to get out more.

    13. Re:I loved antitrust by arose · · Score: 1

      HAHAHAHAHAHA

      They fell for it, now they have to release the movie under the GPL.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    14. Re:I loved antitrust by 222 · · Score: 1

      "ahhhh thats it! they reversed the access code!"
      heh

    15. Re:I loved antitrust by 1lus10n · · Score: 1

      so what your saying is that angelina jolie wasnt hot in hackers ???????

      --
      "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
    16. Re:I loved antitrust by Rogerborg · · Score: 1

      Also the opposite result. And anyone using "non const == const" instead of "const == non const" needs a beating with a cluestick.

      Aaah, nit picking, my favourite pastime.

      --
      If you were blocking sigs, you wouldn't have to read this.
    17. Re:I loved antitrust by tzanger · · Score: 1

      Also the opposite result. And anyone using "non const == const" instead of "const == non const" needs a beating with a cluestick.

      You've gotta be kidding me; the compiler sees const == nonconst differently than nonconst == const?

    18. Re:I loved antitrust by Anonymous Coward · · Score: 0

      Faster? Ooooh, yeah, a few cycles saved in an application at the expense of making it hard to read/debug and maintain. Anyone would think it was the inner loop of a fucking 3d renderer.

    19. Re:I loved antitrust by Rogerborg · · Score: 1

      > the compiler sees const == nonconst differently than nonconst == const?

      No, but it sees const == non const differently from const = non const. Did you see the difference? This is the number 1 typo made by programmers, and the easiest to catch if you just habitually put the const on the left.

      --
      If you were blocking sigs, you wouldn't have to read this.
    20. Re:I loved antitrust by bertrandom · · Score: 1

      I thought Angeline Jolie was hot in Hackers. And if you pause it at the right spot you can see nipples. =)

    21. Re:I loved antitrust by tzanger · · Score: 1

      No, but it sees const == non const differently from const = non const. Did you see the difference? This is the number 1 typo made by programmers, and the easiest to catch if you just habitually put the const on the left.

      True enough, but that's hardly reason to bring out the clue stick.

    22. Re:I loved antitrust by Rogerborg · · Score: 1

      >True enough, but that's hardly reason to bring out the clue stick.

      There's never a bad reason to bring out the cluestick.

      --
      If you were blocking sigs, you wouldn't have to read this.
    23. Re:I loved antitrust by Anonymous Coward · · Score: 0

      As a matter of fact, now would be a perfect time....

  10. Seriously... by Faust7 · · Score: 2, Funny

    On Slashdot? This has to be the grand-slam heavyweight champion of trick questions.

    1. Re:Seriously... by The+J+Kid · · Score: 1

      Yeah, we all know it's what CowboyNeal thinks it is....duh :P

      (this should be a poll btw..)

      --
      Moderation: +4. Modded 70% Funny and 30% Overrated. 100% Saturated.
  11. Hush! Hush! by LX.onesizebigger · · Score: 4, Funny

    As someone who hopes to graduate with a Bachelor of Business Admin and a Bachelor of Science (CS) and has an interest in OSS, my thoughts on this:

    Hush! Don't tell them! OSS will be a comparative advantage to some of us. Don't ruin that!

    (TWAJS)

    --
    I for one welcome our new SCOviet Russian overlords to whom all our base are belong.
    1. Re:Hush! Hush! by Simon+Lyngshede · · Score: 1

      It is not nice, but you got a point. Some of us have ideas of how to make money of Open Source, but we're telling people.

      I'll give you a hint, Open Source is customer power. We need to learn our customers that they should never buy software they don't have the source code for. If you have the code your in control. I think that is what Open Source is all about and once people learn that we win.

  12. GNU's definition by plj · · Score: 3, Interesting

    The article seems to be pretty concentrated to OSS community. But how about GNU's definition of OSS?

    Personally, I think its the license, which answers the question.

    --
    “Wait for Hurd if you want something real” –Linus
    1. Re:GNU's definition by ronfar · · Score: 4, Informative

      Actually, I think here is a more accurate view of the GNU Foundations ideas about Open Source Software.

      --
      All the creatures will die, And all the things will be broken. That's the law of samurai. (Jubai, 1605)
    2. Re:GNU's definition by GMontag · · Score: 1, Funny

      Shouldn't that be GNU/OSS? ;-)

    3. Re:GNU's definition by plj · · Score: 1

      Now when you said it, I have to agree.
      I think I actually have seen that definition before, too. But the GNU license page just popped into my mind instantly, and I didn't just remember the page you pointed out.

      Prepare to get modded up. ;)

      --
      “Wait for Hurd if you want something real” –Linus
  13. Actually explain it to me. by Anonymous Coward · · Score: 0

    Checkboxes

    GPL
    BSD
    Business(You have the code and can change the code but can't resell the code, just used for your project)
    Other

  14. Re:no by Anonymous Coward · · Score: 0

    you have to UNDERSTAND something before you can RESPECT it.

    And it's "you" not "u".

  15. Sorry by BillsPetMonkey · · Score: 4, Insightful

    But on theinquirer, this is preaching to the converted, and the linux side banner "blindingly easy" betrays a lack of objectivity in approach. I'm not trolling, but this article won't be noticed by the people who really need to see it.

    In the area of marketing the "linux zealot" tag is our own worst enemy and unfortunately that's what this will be labelled.

    --
    "It's not your information. It's information about you" - John Ford, Vice President, Equifax
  16. Here's an interesting snippet: by Bame+Flait · · Score: 0, Offtopic

    Vitamin C is a crucial part of dealing with Open Sores. According to Dr. Bob, vitamin C can be used topically for open sores and wounds. When you put vitamin C topically on a sore or wound it can be the equivalent of eating 30-50 thousand milligrams of vitamin C in the bloodstream! Dr. Bob used this mixture on everything including burns, ulcers, cuts, infections, etc. Dr. Bob also advised using an omega 3 and 6 oil blend and mixing it with the aloe vera and ascorbyl palmitate. Dr. Bob recommended Udo's oil from Flora for an omega oil blend. Then put Vaseline over the oil to seal it at the wound.

  17. This is unbalanced advocacy by Anonymous Coward · · Score: 2, Insightful

    Chances are a PHB will have heard some of the anti-OSS FUD that's going around and this article takes no steps to address that. A semi-technical sceptic PHB will dismiss this article.

  18. Not obvious by Jad+LaFields · · Score: 5, Insightful

    As a someone who is relatively new to /., the 'geek scene', and alternative software, I'd just like to point out to many people I don't think that OSS is a very simple, obvious concept. I haven't finished reading the article yet, but I think the idea of explaining OSS simply to 'non-geek' people is a good one, considering the "if you don't know what it is, figure it out yourself, we're not pandering to anyone" attitudes I've seen every once in awhile. Well, off to finish reading...

    --
    [SIG] It's like putting a moose in the blender -- a recipe for disaster!
    1. Re:Not obvious by Milo+Fungus · · Score: 4, Informative

      Agreed. As a greenie geek I spent a lot of time just getting up to speed. To save you some Googling (which is a great way to learn about OS/FS), let me post some links for you. These were articles that I've found particularly helpful.

      Some of these weren't around when I was getting into things. Creative Commons came a bit later. Most of my earliest reading was from GNU. You've already found Slashdot, which is one of the best resources for learning about FS/OS, especially as it relates to current developments.

      One word of caution: FS/OS is a religion. People can be very zealous about their views on it. Be careful as you formulate your own opinions, which will likely change over time. When in doubt, choose a more moderate approach. (If you're interested, my personal views can be found here.)

      I hope this is helpful. Well, off to more reading myself...

    2. Re:Not obvious by blackcat++ · · Score: 1

      As a someone who is relatively new to /., the 'geek scene', and alternative software

      Welcome. Hope you like it here.

      I haven't finished reading the article yet, [...]

      It's quite obvious you're new. Noone here really reads the linked articles. Just read the headline, maybe skim the summary and then post either a "Fuck M$"! post or make a 1. [Headline] 2. ??? 3. Profit! joke. That's how it works here.

    3. Re:Not obvious by Arandir · · Score: 1

      I'd just like to point out to many people I don't think that OSS is a very simple, obvious concept.

      It depends upon how they were brought up. When you've spent your whole life being told "software must be controlled by the author", then it's very hard to grok the concept of open source software. If you don't understand the concept of source code, then understanding the difference between proprietary freeware (IExploder) and open source freeware (Mozilla) is very difficult.

      Although I'm not as old and decrepit at RMS and ESR, I entered the computing world when the whole "everything must be proprietary" concept was just getting started. As a consequence, it was very easy for me to understand the FOSS concept because I had a glimpse of what the computing world was like back before the public got brainwashed by two decades of ZDNet and Microsoft.

      If you find that people are confused, use the analogy of a recipe. If someone asks you for your chili recipe, do you give it to them, or do you tell them they must license it from you under an NDA?

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    4. Re:Not obvious by Anonymous Coward · · Score: 0

      The "author's" rights are not protected now. Unconstitutional contracts are the name of the game.

      What makes you think other wise???

    5. Re:Not obvious by Anonymous Coward · · Score: 0

      Wow. I am amazed by the lameness evident in this post. Wow. Wow. I mean, wow. Just wow.

      Slashdot isn't the best resource for *anything* except for observing the worst sorts of geeks out there. And of course such a collection of losers can provide hours of entertainment for those of us who are bored enough to talk to them.

    6. Re:Not obvious by Anonymous Coward · · Score: 0

      Inept moron

      "lameness"???
      "us"???

      Use your imagination, what little left there is.

    7. Re:Not obvious by Anonymous Coward · · Score: 0

      Welcome Milo, don't mind the trolls, they've developed a culture of their own and he's one of the least.

    8. Re:Not obvious by Shaper+of+Myths · · Score: 1

      1. Greet newbie
      2. Teach newbie Our Ways(tm)
      3. ???
      4. Profit

      Sorry, someone had to do it...=)

    9. Re:Not obvious by MrResistor · · Score: 1

      It depends upon how they were brought up. When you've spent your whole life being told "software must be controlled by the author", then it's very hard to grok the concept of open source software. If you don't understand the concept of source code, then understanding the difference between proprietary freeware (IExploder) and open source freeware (Mozilla) is very difficult.

      It's more fundamental than that, I think. I was born in 1975, and grew up right in the middle of the era you speak of, but FOSS makes more sense to me than proprietary software does.

      Most people are brought up in a very materialistic environment, where the only value anything has is how much money you can get for it. If you're used to thinking of everything in terms of money, of course you won't understand why someone would do something for any other reason. I don't think it has anything to do with ZDNet and MS, though, I think they're just symptoms of the underlying disease.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    10. Re:Not obvious by Arandir · · Score: 1

      I know what you mean. Perhaps it was my rural upbringing that prevented that city materialism from infecting me.

      Sad how capitalism got replaced by corporate materialism in the modern world.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  19. open source is fun by tuffy · · Score: 3, Insightful

    Or, perhaps less simply, it's the notion that writing code for its own sake can be worthwhile - both to the writer and to everyone else.

    --

    Ita erat quando hic adveni.

  20. Quality "Ensurance" by Anonymous Coward · · Score: 1, Interesting

    Is "ensurance" a word?

    Like the authors I'm a Brit so I know the British distinction between 'insure' and 'ensure' but I'd never say 'ensurance', I'd say 'assurance'.

    You know, like 'QA'.

    1. Re:Quality "Ensurance" by Anonymous Coward · · Score: 0

      Like the authors I'm a Brit so I know the British distinction between 'insure' and 'ensure' but I'd never say 'ensurance', I'd say 'assurance'. You know, like 'QA'.

      Oh, hadn't spotted this was footnote 4.

      Even so, I think they've just made 'quality ensurance' up for the article - the only google hits are poor translations into English - and they're being overly anal about their dictionary definitions.

  21. So.. by zapfie · · Score: 5, Funny


    What is Open Source?

    Open Source is patient. Open Source is kind. It does not envy.

    It does not boast, it is not proud

    It is not rude, it is not self-seeking, it is not easily angered

    It keeps no record of wrongs

    Open Source does not delight in evil but rejoices with the truth

    It always protects, always trusts, always hopes, always perseveres

    --
    slashdot!=valid HTML
    1. Re:So.. by Munelight · · Score: 1

      ...and its nose should pant, and its lips should curl, its cheeks should flame, and its brow should furl. Its bosom should heave, and its heart should glow, and its fist be ever-ready for a knock-down blooooooooow.

    2. Re:So.. by bludstone · · Score: 1

      Thank you for the list of things to avoid saying to a business-person when trying to sell them on linux.

      --

      no .sig
    3. Re:So.. by Malibu+Barbarian · · Score: 2, Funny

      This release includes the beta nose. I'm still working on the lips. I had to remove the heart because it didn't work right for anyone but me, still looking at that.

    4. Re:So.. by Anonymous Coward · · Score: 1, Funny

      There remain Mountain Dew, code, open source, these three. Yet the greatest of these is open source.

    5. Re:So.. by Anonymous Coward · · Score: 0

      I think you mean Love...

      I Corinthians 13:4-7

    6. Re:So.. by Anonymous Coward · · Score: 0

      It's the guardian
      It protects
      It satisfies
      It is the one
      OSS

    7. Re:So.. by Anonymous Coward · · Score: 0

      The bosom is a "nice to have"; most users seem to get by without it.

    8. Re:So.. by tanguyr · · Score: 1
      It keeps no record of wrongs
      cvs annotate [-lf] [-r rev|-D date] files ...
      /t
      --
      #!/usr/bin/english
    9. Re:So.. by crazyphilman · · Score: 1

      Looks like a riddle... So, going by your criteria...

      What's patient, kind, not envious, not boastful, not proud, not rude, not self-seeking or easily angered, not prone to record-keeping of wrongs, leans to truth instead of evil, protects, trusts, hopes, and perseveres?

      I know! It's a HOOKER!

      --
      Farewell! It's been a fine buncha years!
    10. Re:So.. by Anonymous Coward · · Score: 0

      Looks like a riddle...

      It's from the Bible. Oh ye of little culture...

    11. Re:So.. by crazyphilman · · Score: 1

      An A/C said, "Looks like a riddle...

      It's from the Bible. Oh ye of little culture..."

      CULTURE? Feh. Culture is what happens when I forget to throw out old chinese food. Usually it's blue, sometimes green. ;)

      --
      Farewell! It's been a fine buncha years!
    12. Re:So.. by evbergen · · Score: 1

      Yep. Love and virtue are foul words to the businessman.

      --
      All generalizations are false, including this one. (Mark Twain)
  22. NO by Anonymous Coward · · Score: 3, Insightful

    Open Source developers have to respect end users before it will be accepted. No more of this "RTFM, j00 n00b. h4w h4w, I 0wn3d j00. 1337."

  23. assumptions by thoolihan · · Score: 5, Insightful

    The author assumes some things. High Quality? Some software is. OpenSSH for starters. However, anyone who's spent some time installing packages on various GNU or BSD systems knows there are some really awful projects out there too.

    Now that I think about it though, thanks to the Java version of ICQ, I think closed source still holds the worst app of all time record...
    -t

    --
    http://unmoldable.com W:"No one of consequence" I:"I must know" W:"Get used to disappointment"
    1. Re:assumptions by RatBastard · · Score: 1

      The problem isn't always "quality" but "completion". I'm always running into programs versioned at 0.4 and 0.9-beta all the time. Even on the better distrobutions. Personally, I'm tired of half-finished programs being distributed as workable solutios when they aren't. The worst is what look like good and usefull programs that have been abandoned by their developers.

      "But you could finish it yourself", some of you are saying. No, that I can not do. I am not a programmer. I have not written a program since 1994 and I have no plans to start again, unless you all want to convert to Turbo Pascal, which I doubt you are willing to do.

      --
      Boobies never hurt anyone. - Sherry Glaser.
    2. Re:assumptions by Anonymous Coward · · Score: 0

      High Quality? Some software is. OpenSSH for starters.

      Sure, if by "high quality" you mean "has had tons of security holes". I like OpenSSH as much as the next guy but there's no need to pretend it's some magic piece of software just because it's from openbsd.

  24. I had... by Anonymous Coward · · Score: 0, Offtopic

    ... Open Sores once. Penicillin cleared 'em right up.

  25. PHB? by Anonymous Coward · · Score: 2, Funny

    Does it make me more or less of a geek that I thouhgt "Player's Hand Book" before "Pointy Haird Boss" when I read PHB?

    1. Re:PHB? by Anonymous Coward · · Score: 0

      It depends on which PHB you're talking about - D&D or AD&D, and then which edition - 1, 2, 2+ or 3.

      If its less than 3, you're OK, +3 extra geek happiness.

      If its 3, -1 n00b g33k.

      If its D&D, +5 l337 g33k g0d.

  26. Authentic by Anonymous Coward · · Score: 1, Funny

    This code segment actually comes straight from dselect.

  27. IMO by Neophytus · · Score: 1

    Open source is any source that is available. open source software is whatever you want it to be

  28. Indeed by Faust7 · · Score: 1

    SCO = Strange Concept, "Open."

    1. Re:Indeed by WeeLad · · Score: 1

      SCO: Same Code as Ours
      SCO: Software costs 0 (zero)
      SCO: Some Company Oppressing
      SCO: Same Crap Online
      SCO: Some Crazy Organization
      SCO: Save Costs. Obtain
      SCO: Steal Code Online
      More? Try some, they're fun.

      --
      Seriously, Don't take anything I say seriously.
    2. Re:Indeed by mav[LAG] · · Score: 1

      BILL GATES, MICROSOFT

      rearranges to:

      IF A TROLL, IBM GETS SCO

      --
      --- Hot Shot City is particularly good.
    3. Re:Indeed by mav[LAG] · · Score: 1

      or even better:

      SAFE SCO-IBM TROLL GIT

      I should send some of these to The Reg...

      --
      --- Hot Shot City is particularly good.
  29. Self-Reliance by Bame+Flait · · Score: 3, Insightful

    Although I posted offtopic flamebait above, I'm moved enough by this post to respond seriously.

    Businesses have a problem these days when it comes to software implementation - people aren't very good at it. This is typically (in my experience), because they have a hard time finding the right people who are expert in implementing software (which in many businesses, is at least as challenging as developing it). This difficulty is compounded when you have to deal with third-parties, which are notoriously unreliable when it comes to satisfying commitments (time, dollars). Those who have the appropriate human capital are the ones best equipped to implement open source effectively - and those who don't, won't.

    Now part of the nature of open source is that there isn't a corporate entity out there that bears some responsibility to the organizations implementing the software - and this is where modern executives run into a wall. Without someone on the inside who knows their stuff, they're not going to be implementing anything other than the same old corporate offerings that will come with (mediocre) software and support.

    What executives need to realize is that open source doesn't just give their programmers more control, it gives them more control. With the right personnel and a little innovation, open source gives you the power to grow and expand your business in highly specialized ways that proprietary software simply won't be able to match - even in a co-development type of environment (this I know from experience).

    So cancel your MSDN subscription, and hire a few competent admins and developers. Then listen to them. It might feel like stepping off the plank into shark-infested waters, but they'll soon realize that they're swimming with the mermaids and dolphins in a sea of technical enlightenment.

  30. What is Open Sores? by AtariAmarok · · Score: 0, Redundant

    Remember the "Foxtrot" cartoon, where the mother mis-heard her son's reference to open source as being "Open Sores".

    --
    Don't blame Durga. I voted for Centauri.
  31. Missing the Point by Delphix · · Score: 5, Insightful

    While I read slashdot daily, and have an appreciation for Open Source software, I think a lot of you miss the point. I work for a company that builds 3D simulations. For years we used IRIX. SGI was simply the best graphics rendering stations you could buy. We still have some fridge sized boxes, an old Octane, and a couple O2s sitting around.

    However, we've moved to Linux. We use Red Hat 7.2. Why? Because Open Source is great? Beacause we're giving back to the community? No. Because Linux allowed us to reuse all our simulation code that was built using Unix interoperabilty on more modern hardware, cheaper. We can go grab a GeForce4 Ti 4600 off the shelf, get a 8MB Buffered IDE HD, and Dual Athlon chips and they'll eat those O2s / Octanes, and even the old fridge sized Onyx. Slap six of them together and you've got a six channel renderer. We did have to change our IG software. We were using Performer, now we use a third party developed renderer.

    For years our the company that developed our renderer has supported both Linux and Windows. Now they only support rendering on Windows. They still support the API for Linux though. So now we're looking three options:

    1) Devoting time to developing our own Linux based renderer.
    2) Continuing to use their API on Linux, but to control chanels on Windows boxes.
    3) Converting the simulation over to Windows and dropping Linux.

    At this point option 1 is pretty much out. While we have the in house skills to develop an IG, it would take several years to build something to meet our requirements (needs texture paging, terrain paging, must handle terrain sizes in excess of 2GB, etc).

    Option 2 looks attractive because it's the least work. And will probably be what's implemented in the short run.

    Option 3 will probably be our long run solution as we've had some trouble with nVidia and ATI drivers on Linux. While they do work in most cases, they don't seem quite as robust as their Windows counterparts. Ie with the Quadro cards...

    Now if you go back and read over these things, what we considered in deciding what to use were:

    1) time
    2) cost
    3) ease of implementation

    You'll note we never said anything about Open Source. When we first moved to Linux we looked at Open Source issues. We use open source development tools. GCC, GIMP, ImageMagick, Glade... But it had nothing to do with the fact they were open source. If they had been sold to us like IRIX was and performed the same functionality we would have bought them.

    We're interested in shipping our product, making $$$, and that's what managers are concerned with. The debate over whether or not we use Open Source software is irrelevent. The questions that have to be answered are how it would impact cost, time to delivery, learning curve. The other thing is, you shouldn't expect businesses to go out and just switch to Open Source because you wrote a persuasive article. If there is a system in place, it probably won't be replaced until it's necessary to do so. It's that whole cost thing again. Why replace something that's been paid for that works until it's necesary to do so.

    If you answer that with anything other than it will make the company more $$$, or increase productivity, etc... you won't get very far with the suits.

    1. Re:Missing the Point by Surak · · Score: 1

      Just a little side note here:

      We did have to change our IG software. We were using Performer, now we use a third party developed renderer. For years our the company that developed our renderer has supported both Linux and Windows. Now they only support rendering on Windows. They still support the API for Linux though.

      But I'll bet the company that developed your renderer now has their hands in Microsoft's back pocket.

      For years, Unigraphics (currently owned by EDS), was available on RISC-based Unix workstations only. They wanted to develop the stuff for Intel processors, so the first Intel platform they ported to was Solaris x86. They had a fully-working Linux port in progress. Then they started doing a Windows port. The first Windows port required Hummingbird Exceed (or other X server) to be running on the NT machine. Well, Microsoft jumped in, gave them free developers and free development tools and other free resources to make their Windows port into a logo-compliant application. They immediately dropped the Linux port, and rumours have it that they are dropping the Solaris x86 port. If it weren't for their existing customer base, they'd be dropping their Unix ports too.

      Much the same story for CATIA and SDRC (now EDS, coincidentally?) I-DEAS.

    2. Re:Missing the Point by Anonymous Coward · · Score: 0

      1) Devoting time to developing our own Linux based renderer.

      1-b) Use existing OSS as a base to develop an Open Source renderer and benefit from 3rd party contributions to the codebase.

      [...]

      5) Profit$$$

    3. Re:Missing the Point by maraist · · Score: 1

      but the key is, will they net more money in the long run. Writing software is almost trivial.. Maintaining it is where the costs come in.

      Sticking with 3rd party software means that you can plan towards upgrades as you need them. I admit that the disadvantage is, just as this company has experienced, you are at the mercy of what they want to support.

      That being said, there's typically a good reason to not support a platform.. If it's too expensive for them to maintain and too few customers, etc. Or having issues keeping working environments going (read the many distributions needing support).

      It's a shame, but I don't really blame either this company or the 3'rd party company.

      --
      -Michael
    4. Re:Missing the Point by Anonymous Coward · · Score: 0

      what is an IG?

    5. Re:Missing the Point by Delphix · · Score: 1

      An IG is an Image Generator. It's basically just a 3D render that is slaved to some other processes sometimes via ethernet.

      Instead of dealing with all the rendering code yourself, you call into an API and say something like:

      model MyCar;
      InstantiateModel(MyCar,"/home/databases/co mmon/MyC ar.flt", X, Y, Z, Heading, Pitch, Roll);

      Relocate(MyCar, X, Y, Z);
      Rotate(MyCar, Heading, Pitch, Roll);

      then you can do special effects like:

      SpecialEffect(MyCar, ON_FIRE);

      It comes with 3D models for doing things like fire, smoke, missile trails, etc. You just tell it you want it on fire. Maybe pass an offset from your model or a size of the fire, etc.

      Those are of course just examples... not a real API. Generally it takes in to account quite a bit more, such as velocity and acceleration vectors for dead reckoning until the next update is received, etc..

    6. Re:Missing the Point by Delphix · · Score: 1

      Actually it's not a Microsoft issue. Well, it is, but not quite how you describe it. They're not getting anything from Microsoft or migrating towards DirectX. They're actually very big proponents of OpenGL. However most of their customers develop on Windows Platforms.

      The problem is more related to the fact we're one of the few people who actually use the Linux version of their Renderer. We own a site license and do some debugging for them, but it really doesn't cover their cost to produce it. They can maintain it because there is a lot of code reuse between Windows and Linux due to the fact of using OpenGL.

      It sort of works like this:

      We don't develop our own renderer because we'd end up paying 3-4 software engineers 80-100K a year to develop and maintain it. Where as we can obtain a site license for about $75,000 flat. We upgrade about once every two years to a new major release and get fixes for free inbetween, so it's about $27,500 a year to maintain the IG. So there's a rather sizable cost savings to using a pre-made solution and not making our own. ($27,500 per year vs. $240,000 -> $400,000) Of course we the cost we pay is that they can in a way dictate our architecture.

      The problem for them is that we're one of the two customers who use the renderer on Linux. So they're expending quite a bit of resources for us, and on one other company. Where as they have quite a few Windows customers. So for them it's beneficial to migrate to Windows only and utilize their resources there.

      In this case, they're doing what their clients are requesting. Developing an IG to meet their needs, ie: on Windows. (at this point the debate between MS technologies becomes academic. Most simulation vendors couldn't care less if the thing uses OpenGL, DirectX, or whatnot as the back end API. They're just interested in "can it render my X GB database at X Hz? does it support the special effects I need? how easy is the API to use? how many channels can i control simultaneously from a single process?") Although for the time being, they're supporting the API on Linux, so we can keep our simulation on Linux and migrate the rendering channels to Windows.

      In the end though, it's still looks advantageous for us to move over to Windows. All the engineers who develop / maintain the simulation are still with us. They're very familiar with it's inner workings and most are familiar with both Windows and Linux. So for us it seems more beneficial to eventually migrate our simulation to Windows.

      The real problem we see in the future is that if Linux doesn't catch on and continue to provide reason for companies like nVidia to continue Linux development, they may drop support for their drivers on future cards, just as our IG vendor is starting to. For us that's not a good gamble. We can't afford to get stuck using generation old technology. We push our hardware to the limit as it is.

      The one great benefit of moving to Linux and the PC is that we can immediately take advantage of new hardware as it becomes available for relatively little cost. It's now starting to look as though we may need to move towards Windows to continue to have that benefit.

      On the horizon right now I see PCI Express (PCI-X) as technology that we'd want to take advantage of. Especially in conjunction with Serial ATA (yes, you can get that right now for PCI). In that migration, will Linux drivers be available for PCI-X cards we use? Now that Apple has gone to the desktop with 64-bit, the PC will probably see that transition within 2 years. How ready is Linux to deal with Intel and AMD's 64-bit offerings?

      I've rambled on, but you can see some of the questions that we ask ourselves as we consider our development path. Also some of the reasons why we've come down the path we have.

    7. Re:Missing the Point by _Sprocket_ · · Score: 1


      For years, Unigraphics (currently owned by EDS), was available on RISC-based Unix workstations only. They wanted to develop the stuff for Intel processors, so the first Intel platform they ported to was Solaris x86. They had a fully-working Linux port in progress. Then they started doing a Windows port. The first Windows port required Hummingbird Exceed (or other X server) to be running on the NT machine.


      One of my first responsibilities at a certain major US Government agency was administering a small lab of HP/UX machines running Unigraphics. One of the designers wanted to try out that very same WinNT solution. He got the funding, made the purchase, got everything running... and then asked for his old HP/UX workstation back within 4 months of use. It was a horrid solution.

      Now - this was quite a few years ago. I hope Win2K helped deal with some of the issues. And I'd also hope the software itself improved with time.

      However, oddly enough, the engineers seem to really like their Unix work environment. The Engineering directorate is doing a lot of stuff with Linux - going for Unix-like environment and commodity hardware. If this trend continues (and I understand it is increasing momentum), then vendors like EDS will loose out. But that's OK. There's always been a Unigraphics / ProE jihad going on here. Looks like ProE just might win after all.
    8. Re:Missing the Point by Surak · · Score: 2, Interesting

      It's gotten better, but one of the major problems is the 4GB limit. Specifically, Win2K lets you have 2G of user space. Basically it boils down if you want your assemblies to much larger than 1.5-2GB, forget it. The whole system starts bogging down at 1.5 GB, and when you hit 2GB the system dies and throws up its hands. Needless to say, many product designers at a certain major auto manufacturer are still running on Solaris boxes. Microsoft, of course, has been profusely promising a fix, but still haven't delivered of course.

      Pro/E of course will eventually run on Linux, :)

      One problem is the GM IS&S directorate that no open source software shell be used. This came, interestingly enough, right after they began to move to Windows platforms for Unigraphics. More interesting is that their servers all run HP-UX, and that they integrate with their existing Win2K DFS system using CIFS 9000. Hmmm...no open source, huh? (For the uninitiated -- CIFS 9000 is just Samba relabelled by HP)

      Ah well. I did the best I could to advocate Open Source while I was there and was told to just 'drink the kool-aid.' *sigh*

    9. Re:Missing the Point by Surak · · Score: 1

      In that migration, will Linux drivers be available for PCI-X cards we use? Now that Apple has gone to the desktop with 64-bit, the PC will probably see that transition within 2 years. How ready is Linux to deal with Intel and AMD's 64-bit offerings?

      Good point. I dunno. Linux runs on Opteron now, I don't think it's much of a problem to move it to Athlon64. Linux is also running on Itanium as well. I don't know about PCI-X hardware, but there *is* a patch available for 2.4.20 kernels for PCI-X hotplug support that I've seen bantered about on the lkml, so I gotta believe that PCI-X drivers for invididual cards can't be THAT far behind. And Pogo Linux, Inc. has released Serial-ATA drivers already, so I don't think that hardware support is lagging behind Windows nearly as much as it was in the early days, and in some ways it's BEATING Windows (Linux had Itanium and Opteron support FIRST, for instance)

  32. AntiTrust is the worst movie since the Matrix. by HanzoSan · · Score: 1, Funny



    Anti Trust had no plot, the hacking wasnt even real, most hackers use Windows. Also Microsoft, I'm assuming this is who the movie wanted to imply it was about, is one of the most honest corperations on the face of the earth, they support affirmative action and have donated millions of computers running billions of dollars worth of the best most well known software.

    Bill Gates also gives scholarships, gives money to India, Africa, China, Europe, this man should be knighted.

    --
    If you use Linux, please help development of Autopac
    1. Re:AntiTrust is the worst movie since the Matrix. by Anonymous Coward · · Score: 0

      Your trolling is just a little too obvious with this one. Your usual persona as deluded dimwit is undercut by this, more bizarre, statement.

    2. Re:AntiTrust is the worst movie since the Matrix. by Richy_T · · Score: 4, Funny
      Bill Gates also gives scholarships [...] this man should be knighted.

      Certainly someone should be waving a sword in the vicinity of his neck.

      Rich

    3. Re:AntiTrust is the worst movie since the Matrix. by Drakonian · · Score: 1

      Have you turned over a new leaf or something? Normally your trolls are more subtle!

      --
      Random is the New Order.
    4. Re:AntiTrust is the worst movie since the Matrix. by Anonymous Coward · · Score: 0

      Honoring Bill Gates for donating money is like honoring Jeffrey Dahmer for organ donation.

    5. Re:AntiTrust is the worst movie since the Matrix. by Blind+Linux · · Score: 1

      Ryan Phillipe is cooler than you.
      When Ryan Phillipe is cooler than you, you know you have a problem.

  33. Open Development by eadz · · Score: 3, Insightful

    is what open source is really about. I have seen quite a few "Open Source" projects - code released under the GPL - that have been closed development and absolutly useless as an open source project because of this.

    1. Re:Open Development by monique · · Score: 1

      I agree that it's nice to have open development, but with an open source license, you don't need the original developers to welcome you -- all you need is someone willing to spearhead a new effort.

      If a development community isn't willing to play nice, you can always branch off and use their code to start your own open community.

      Sure, it's easier (and cleaner!) for the original development group to do this for you, but if they won't, you do have a choice.

      --
      -monique
  34. Re:NO by Anonymous Coward · · Score: 1, Redundant

    Ya the problem is when you use open source software long enough you get used to its "something always needs to be fixed" ways. There's always something that needs tweaking or configing or editing. Nothing ever just works. The problem is the developers have been doing this so long they don't realize it's so bad. Also most of the hardcore users of open source software enjoy this, they think it's fun to always be tweaking and fixing and editing. Sure to them it probably is. I just want a desktop that works. I use GNU/Linux sure, but it definatly needs work if anyone is going to use it on the desktop.

  35. What is open source? by The+Bungi · · Score: 5, Funny
    That most interesting of human endeavors whereby some people give away the fruit of their labor and get nothing in return. The idea here is that "closed software" is an anathema to human freedom and therefore clashes with the pursuit of life, liberty and well-cooked apple pie.

    A theory formulated by people who came to age trying to screw universities out of what they considered their own personal property, which was then somehow extrapolated to the real world and subsequently swallowed in extremis by a few technically capable idealists and several million people looking for a free ride who contribute absolutely nothing but "believe" and therefore are part of the "community".

    The resulting movement (and its derivatives) can be thought of as the technological version of the catholic church during the depth of the medieval era - in both structure and radical "join us or die" behavior.

    Along the way they convince themselves that "some day" they'll make a buck on giving away stuff, and when they don't (which is the most common result), they blame the government, the system, the corporations and the weather for being "unfair".

    Basically.

  36. Company-to-Company relationships are important by TopShelf · · Score: 4, Interesting

    That's an interesting point that many people overlook - just because IBM supports Linux doesn't mean that IBM makes a good partner for smaller businesses.

    A couple years ago I was part of a vendor selection process for a WMS, and one the three contenders (EXE) basically eliminated themselves by not demonstrating that they took customers of our size (~$200 million) seriously. I sent them data to use for our scripted demo weeks in advance of our visit, only to have their technical sales rep get back to my voice mail with initial questions at 5:30 p.m. the day before we were to arrive - and by that point I was already on the plane. The demo, obviously, turned out underwhelming.

    Their functionality was top-notch, but all the signs were that we'd be a small-ish customer to them, and hence not worthy of focused attention (read: flunky implementation consultants among other issues). A major component of any software purchase decision has to be the potential relationship between the customer and vendor, and how well the customer feels they'll be treated going forward...

    --
    Stop by my site where I write about ERP systems & more
    1. Re:Company-to-Company relationships are important by Huk · · Score: 2, Interesting

      IBM supports Linux, because there is money in it. They would support commodore 64s if there was money in it. To believe that they feel Linux or Open Source software was somehow better would be naive.

    2. Re:Company-to-Company relationships are important by MikeD83 · · Score: 1

      IBM and Sun would both rather you work with value added resellers. They prefer this model because it keeps their service costs lower and offers you the best service possible through your small to medium sized VARs. You also won't save any money going direct from the manafacturer either.

  37. Mod parent down, -1 troll by Anonymous Coward · · Score: 0

    WTF does Irag have to do with open sores?

  38. you have it exactly by zogger · · Score: 2, Insightful

    You nailed it. It's a HUGE economic and practicality advantage in most cases for businesses. If they can maintain their competition (somehow) to keep using the expensive buggy stuff, they can pull ahead quickly. And even better if they completely "get it" and share back, they'll have the help and interest in their products they deserve, their business will do better, they can make more money and pay the help and stockholders more..on and on. I'm amazed that businesses still cling to that which just costs and costs and costs and costs and never really delivers all that well. Let em fail I say.

  39. sorry by Oldskooldave · · Score: 0, Offtopic

    your g5's coming with jaguar not panther my "1337" haxor friend

  40. It's a Start by tomakaan · · Score: 1

    A lot of businesses and schools enjoy spending money for some reason. It gives them a false sense of security. And, of course, it can't be good if it's free. Everything that is free is too good to be true.

    I think that as more and more of these types of efforts come around, the movement towards seeing open source more widely used will pick up a little speed (as with everything else). Sure, it's only The Inquirer and some computer maintenance company in the UK, but ya gotta start somewhere.

  41. One misconception I had by jcsehak · · Score: 4, Insightful

    One misconception I had was that open source meant you had to give the product away for free. This was even reflected in version 1.0 of the Open Source Music License I wrote (that I based on the GPL). But that's not so! You only have to give the source away, not the end-product. And you don't even have to make it available for download, you need only sell people CDs of the source for the cost of the media.

    Open source isn't so much for the benefit of the end-user as the developer. Or rather, other developers. So it's just as easy to make money on an open source project as a closed one, as long as someone else doesn't take your code and make their own version that better and cheaper. So for MS, open sourcing Word would be a bad idea. But for a musician like myself, "better" is relative. So making your music open-source does nothing but good.

    --

    c-hack.com |
    1. Re:One misconception I had by GreenBugsBunny · · Score: 2, Informative

      One misconception I had was that open source meant you had to give the product away for free. This was even reflected in version 1.0 of the Open Source Music License I wrote (that I based on the GPL). But that's not so! You only have to give the source away, not the end-product. And you don't even have to make it available for download, you need only sell people CDs of the source for the cost of the media.

      Actually, this isn't exactly accurate either. You only have to provide the source code to those who have access to the binary code. You could modify or create any GPL software to your hearts content. If you didn't distribute the binary, you don't have to distribute the source. If you sell the binary, you only have to make the source available. I believe you can even withold the source until it is requested (don't quote me on that, though). If you make the binary packages available for free, you must make the source available.

      Of course, you can just distribute the source. There's nothing requiring a binary distribution.

      Also, you can sell your product for whatever amount of money you want. As long as you make the source available. Whoever buys your software has all of the rights they have to any GPL software, though. They could modify your software and distribute it for free if they wanted to.

      The GPL is all about removing restrictions on who can or cannot use the software. Sure you can charge for the software, but that doesn't stop anybody who buys it from giving it away.

    2. Re:One misconception I had by jcsehak · · Score: 1

      You only have to provide the source code to those who have access to the binary code.

      That's true - I forgot about that; thanks. I've been giving away my binaries for free, so I've been giving making the source available to everyone. I think you're right in that you have the option to not give away the source until it's requested.

      I wonder if I play a GPL'd game over the web, does that mean I have access to the binaries, and therefore have a right to the source, even though I can't get the binaries - It's just say, a Flash game or something?

      --

      c-hack.com |
    3. Re:One misconception I had by poot_rootbeer · · Score: 2, Interesting


      Having gone and taken a look at your Open Source Music License", I disagree with your definition of what "source" means as pertaining to music.

      The way I see it, any audio recording of a piece of music IS the end product. It's a performance of the 'source', which is the words and notes that comprise the music itself.

      Even copyright law makes a similar distinction -- the copyright of a song pertains to the chords, lyrics, printed sheet music of a song; the phonographic copyright pertains to recordings of the song. If you make a copy of an audio recording, you must get permission from the phonographic copyright holder; if you record a song yourself that was written by someone else, you must get permission from the other kind of copyright holder (under US Copyright Law there are conditions where licensing is compulsory, but I digress).

      My conception of a GPL-like music license would be one where artists could sell CD's containing recordings of their music. They would not have to allow people to make their own copies of the CD's, but they WOULD have to provide 'source code' for their music (as lyric files, sheet music, MIDI, or some other conceptual representation) and allow people to make their own recordings of the music, provided the orchestration/interpretation/whatever changes were documented in the 'source' and distributed along with the rerecordings.

      There are at least a dozen different open music licenses listed on the EFF site, I bet at least one of them contains exactly what I've described. But it does demonstrate a concern about open-source movements -- what is the most appropriate way to apply computer programming concepts like 'source', 'binary', and 'compile' to fields that are not computer programming?

    4. Re:One misconception I had by jcsehak · · Score: 1

      I have to disagree with your disagreement. If the source is the resulting binaries, or the notes and lyrics therin, then who cares if you give out lyric sheets and sheet music? They're both easy enough to reverse engineer anyway. If you don't have the original source audio, you can't make minor improvements (replace the guitar solo with your own, put a new beat behind it, etc.). Open source my way is way more fun.

      --

      c-hack.com |
  42. The enquirer? by ocie · · Score: 0, Troll

    Did someone see an image of the virgin Mary, or St. jude in the linux kernel sources?

    --
    JET Program: see Japan, meet intere
  43. ya, so what? by zogger · · Score: 1

    so what if half the projects aren't finished? that means the other half is, and with thousands to choose from, anyone can find what they need. And which is better, finding something your business can use then you can take it from there and more-easily customize to suit, or be forced to pay for a closed source solution that you still have to do that with? Most even expensive closed source programs still require customization, I see the articles here describing all these various expensive programs, they still need admins and coders to make them work exactly how the company wants them to work. One way, the open way, is in most cases cheaper and easier, the other is much more expensive and harder to customize. Gee, tough call there.

    1. Re:ya, so what? by Anonymous Coward · · Score: 0

      i get support when I buy a closed source solution

    2. Re:ya, so what? by efextra · · Score: 1
      half-finished software projects
      half the projects aren't finished
      zogger, I think you missed missed the difference between those.
    3. Re:ya, so what? by zogger · · Score: 1

      half-or some large number- aren't finished. half or some large number are finished or completed *enough* to be useable.There's enough to use most likely, not for every single minute last possible thing you might need software for, but geez loweez there's enough to do the bulk of what needs doing. I fail to see the huge disadvantages. As to "support" (for the AC above), it's there, perhaps anyone using an open source piece of work can hire the actual code writer who started it for support, cash talks in this land, and judgiong by what I read here on slashdot, there's bunches of guys who would appreciate even part time work and might stay on call for support. Ya never know until ya ask or look. And the deal is, open source IS being used, that means people have found out how to deal with support.

  44. Jeopardy! by los+furtive · · Score: 1

    The Answer: James Brown

    The Question: What is 'What it is'?

    --

    I'm a writer, a poet, a genius, I know it. I don't buy software, I grow it.

  45. Re:What is open source? by Anonymous Coward · · Score: 0

    Score: -1, Anti Open Source

  46. Quality? Not. by Animats · · Score: 5, Interesting
    High Quality? Some software is. OpenSSH for starters.

    Only some of the time. One big problem with open source software is that there's only so much attention to go around. High-profile projects like the Linux kernel and Apache get that attention. But once you get past the top 25 projects or so, attention is limited and quality becomes spotty.

    The biggest problem is mid-level open source software that's useful but contains some major design error. It's almost impossible to fix such things. Those projects don't get the attention needed for a major rewrite, and the "patch" approach doesn't generate a redesign.

    CVS is a good example of this. It's a basically good idea, implemented badly. CVS is a client/server system with a database back end. But the client/server system is ad-hoc, as is the database system. CVS clients look for specific text messages coming back from the server; there's no proper client/server protocol, not even error codes. The "database system" is just a collection of data files, lock files, and status files, which can get out of sync.

    "Subversion" was written to deal with these issues. When it's done, it will do about what CVS does, but hopefully better. That indicates a failure of the patch-based open source process. CVS couldn't be fixed within the process; it was necessary to start a new project and rewrite.

    Below the projects that are marginally successful is the dark underside of open source, the thousands of dead and moribund projects on SourceForge. The SourceForge people like to boast about how many projects they have, but for most of them, they're just providing free hosting for trash.

    1. Re:Quality? Not. by Cereal+Box · · Score: 1

      Excellent post. Wish I could mod you up.

      People (well, Slashdot "people") tend to automatically associate "open source" with "quality". Yes, in theory the more eyes you have looking over code and the more people you have making fixes and enhancements will yield an optimal product. But, like you said, few projects are high-profile enough to receive such attention.

      One point you forgot to mention is the tendency for open source projects to splinter off, creating confusion and lack of standardization. Everyone's got access to the source and all it takes are a few people who don't like the way the original program does something (or the way a derivative program does something) and -BOOM-, there are suddenly multiple spinoffs from the original program (and spinoffs from those spinoffs), each with their own way of doing things, creating incompatibilities amongst each other.

      This is one aspect of open source that I find the most frustrating. Instead of trying to make a single program better, there's a tendency to make multiple versions of the same program that each are better than the original in the some way but mediocre in comparison to the original (or derivatives) in some other ways. Come on! Resist the temptation to branch off projects simply because "it's your way" and try to find a way to make the original project work better.

    2. Re:Quality? Not. by CERonin · · Score: 4, Interesting
      Below the projects that are marginally successful is the dark underside of open source, the thousands of dead and moribund projects on SourceForge. The SourceForge people like to boast about how many projects they have, but for most of them, they're just providing free hosting for trash.

      The "dark underside" you refer to exists regardless of the development model. I can't tell you how many projects I've worked on in the "real" (read "commercial") world that went exactly nowhere. The difference, of course, is that these "real" projects (and, occaisionally, a career or two) would die a quiet death in a shallow grave in a cubicle, rather than in public on freshmeat.

      IMHO, the mortality rate for OS projects is just about right. And try not to think of failed projects as "trash". Think of it as rich loam, the vital compost that will spawn new (and possibly) better OS software. Or not ;)

      --
      stirring the pot since nineteen mumblty mumble...
    3. Re:Quality? Not. by Anonymous Coward · · Score: 0

      > "Subversion" was written to deal with these issues. When it's done, it will do about what CVS does, but hopefully better. That indicates a failure of the patch-based open source process. CVS couldn't be fixed within the process; it was necessary to start a new project and rewrite.

      No, this indicates a failure of CVS. No kind of software development process can fix a design that's broken - that's the Whole Point of starting a new design. "Patch-based open source" has nothing do do with a failure of design.

    4. Re:Quality? Not. by thoolihan · · Score: 1

      I think you only read the part of my comment you quoted. If you'll read the rest, you'll see I'm saying that there are a lot of bad-half finished projects out there in the ports and packages sections of the various distros (along the lines of your CVS rant).

      Regardless, I'll add that since this is supposed to be for business managers, quality is important. Sometimes the opensource community has it(apache, openBSD, Grub), sometimes it doesn't. However, many hobbyist and slashdotters are big on opensource for other reasons (less bloat, flexibility, ideology).

      -t

      --
      http://unmoldable.com W:"No one of consequence" I:"I must know" W:"Get used to disappointment"
    5. Re:Quality? Not. by mustangsal66 · · Score: 1

      Wait... This sounds like flamebait but...

      Can you name 25 high quality closed source programs?

      There are a ton of good quality open source programs. The difference is if you find an open source program that does 95% of what you want it to do, you can build the other 5% yourself. Try that with closed source software.

      As for CVS, while not my favorite software versioning system, it does it's job. Your welcome to write a better one though.

      And there are a ton of crap at download.com.

      Oh sure... Awstats, BitTorrent, phpMyAdmin, webmin... etc. Yeah they're all "trash".

      Is there crap on sourceforge... oh yeah, as well as dead projects. But the same can be said for closed source. The big difference as I see it is, if you find a dead open source project, you can pickup the ball and run with it. You can't with closed source.

      --
      Why worry? Each of us is wearing an unlicensed "nucular" accelerator on his back.
      Sig changed for readability by G.W.
    6. Re:Quality? Not. by bullestock · · Score: 3, Informative
      Below the projects that are marginally successful is the dark underside of open source, the thousands of dead and moribund projects on SourceForge. The SourceForge people like to boast about how many projects they have, but for most of them, they're just providing free hosting for trash.

      True, and SF has recognized this - they have recently announced that they will start purging projects with no activity.

    7. Re:Quality? Not. by Dalcius · · Score: 1

      I don't know that I agree with that. In my humble opinion, Gaim is one of the best pieces of software out there. It's flexible as hell, fast, configurable in many ways, and in just the right areas, and has some really useful features (buddy pouncing, multiple accounts on different services, spellchecking, aliasing, etc.). All that and I still feel like it's one of the most user friendly applications for Linux. And Windows.

      They list 7 people as "developers" and another 5 as "contributors". How much or how little each of them develops/contributes I don't know, but I get the feeling that this isn't a "major project".

      Maybe our opinions differ, maybe this is just an isolated example, but I've worked with enough tiny projects that have helped me quite a bit to feel comfortable saying that there is a wealth of projects under the top few that rock the house.

      As for the 'dead projects', we can go into the ratio of dead/alive closed source companies compared to that of OSS projects. We can even bring in CS shareware if you like. :)

      Please feel free to correct me if I'm missing something. :)

      Cheers

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    8. Re:Quality? Not. by ichimunki · · Score: 1

      Yes. I can think of 25 high quality closed source programs. Should I start by listing every video game I've ever played or the many applications that I've found useful over the last 25 years?

      Other than that, I strongly agree. It's nice to have examples of what didn't work, or to have something to look at for ideas, or whatever. The Free Software graveyard is nothing for the community to be ashamed of.

      --
      I do not have a signature
    9. Re:Quality? Not. by tcopeland · · Score: 1

      > the thousands of dead and moribund
      > projects on SourceForge.

      These are not a problem. Almost by definition, a dead project takes up very little disk space and consumes little or no resources.

      The reason there are so many dead projects is that the barrier of entry is low. If I submit a new SF project proposal that says "Here's a Doom clone" and make it sound interesting, SF will grant the request. I might be the next Romero, in which case everything works great and there'll be tons of activity. Or I might be fooling myself, in which case there will be 20 KB of space in a DB2 database devoted to my dead project. Either way - I've had a chance to try. It's a good deal.

    10. Re:Quality? Not. by pyrrho · · Score: 1

      >That indicates a failure of the patch-based open source process. CVS couldn't be fixed within the process; it was necessary to start a new project and rewrite.

      it doesn't, this is it's advantage. With commercial software you write the same solution over and over. I cannot use a solution I've written somewhere else, so I have to start from scratch. Instead of take a system to it's logical conclusion and limits, I make the same system again, because at least it's known what I'll get when I've built it.

      With OSS systems, you follow a system to it's logical conclusion. Then, only when the design is exhausted, do you need to start over. You only replace a system when you need to. In commercial software you are always reproducing systems.

      For nearly all my carreer I've used a lot of commercial tools, and they are simply not as reliable in the long haul as free software is for these sorts of reasons.

      If we get people used to this, to heck with all of you... I'll be able to create a portable library that I can use the rest of my life wherever I work, whatever I do! sounds good to me.

      --

      -pyrrho

    11. Re:Quality? Not. by Anonymous Coward · · Score: 0

      One big problem with open source software is that there's only so much attention to go around. High-profile projects like the Linux kernel and Apache get that attention. But once you get past the top 25 projects or so, attention is limited and quality becomes spotty.

      Keep in mind that smaller projects require less attention in order to produce quality. If you're looking for quality in less popular stuff, look at the tiny projects, where ambition has not outstripped ability.

    12. Re:Quality? Not. by hughk · · Score: 1
      I would challenge that "top 25" that you talk about. There are a lot of good programs out there within the top 100 if not further down the activity scale.

      I agree that CVS is a good example of how the process works, but you should be more favourable to it. Someone produced a solution and it hit a dead-end. It is still adequate for a lot of people but it isn't ClearCase. However, all that code is available for refactoring into another project which will be better. Such a solution is not possible for closed source software unless it is within the vendor.

      I would suggest that you look at another project: GnuCash which has changed massively over its lifetime. Stable releases were just that and the implementation details largely opaque to the user. EFfectively, between stable 1.6 and 1.8 was a massive fork. All managed with CVS.

      --
      See my journal, I write things there
    13. Re:Quality? Not. by evbergen · · Score: 1

      "Subversion" was written to deal with these issues. When it's done, it will do about what CVS does, but hopefully better. That indicates a failure of the patch-based open source process. CVS couldn't be fixed within the process; it was necessary to start a new project and rewrite.

      Well, subversion is also an open source product. It follows that open source is capable of generating redesigns as well as patches, which makes your argument moot, really.

      Nobody in their right mind is arguing that patches are all you need in software. I think the idea that open source can come up with solutions for every software need still holds though.

      --
      All generalizations are false, including this one. (Mark Twain)
  47. Interesting article... by Pettifogger · · Score: 3, Insightful
    I don't know why it hasn't been pointed out yet, but the people who wrote this article are with Olliance, which is *selling* open-source services. Now, before you light your torches and get your pitchforks, I use Linux on a daily basis and do what I can to evangelize the movement. I also have a small collection of aging but much loved Macs. There are no Microsoft products in my household. But as someone who works in business, the first thing I noticed is that this is a sales pitch. Nothing wrong with that, but I know that many others in the business community will see a bunch of red flags because of it.

    I think the biggest reason keeping businesses from switching is inertia or fear of new things. Everything sort of works right now (if the system goes down, the CEO and/or Board of Directors blames IT, not management) but if management makes a switch to something else entirely and it doesn't work, they're going to lose thier jobs. Trust me, software decisions aren't just based on price, stability and features. Even though Microsoft products sort of work most of the time, they're still beating the fear of the unknown.

    For this reason, I really think that Linux/OSS should be pushed on the desktop level. When consultants, like Olliance, come in to install OSS at a company, I think they should put up fliers offering to install Linux on employees' *home* computers, too, if they bring their boxes in. I think one of the greatest unrealized benefits is Walmart selling inexpensive Linux boxes in its stores. That reaches a lot of people, even executives. When they see that it's stable and working and not "scary," it will become viable alternative. Finally, I think some kind of gimmick, like maybe using Linus' birthday as "Linux Day" where everyone who uses it goes to the Mall or somewhere with a bunch of CD-Rs burned with a distro and gives them away to anyone who wants it. The media might even be persuaded to cover something like this. It would spread the costs of producing discs and distribution out over a lot of people. People regularly share their music, why not operating systems, too? I don't know if that would work, but something needs to be done to get OSS onto as many desktops as possible. That's where the real battle for hearts and minds is, and if a CEO (or other high exec) has Linux at home and loves it, you know what will happen at his/her business shortly.

    --

    IAAL

  48. please stay on topic dimwit. by Anonymous Coward · · Score: 0



    We all know these mods are communist and want to mod up liberal posters while modding down conservatives. Havent you learned how the system works?

  49. Education, lots of education by heironymouscoward · · Score: 5, Insightful

    Sometimes what is most obvious to one person is most unobvious to another. OSS is - to Slashdotters - as obvious as water and sun. To managers, it is a contradictory concept and much of the education has to come in the form of explaining why it is "free". Much of the counter arguments to OSS try to leverage the natural paranoia of business people (GPL virus, OSS patent liability, TCO, etc. etc.).

    The simple truth - and this is obvious to any neutral observer - is that the Internet changed the dynamics of the software industry by removing all the previous barriers to organization and communication. What used to require a large organization to produce can now be economically (and this is the key) produced by random professionals in their spare time, by tiny teams working on thin margins, and by organizations who would otherwise do nothing special with the code anyhow.

    The key questions about OSS ("who pays?") have been asked before, about the Internet, and we now all know the answers: everyone pays, a little, but since the technology required is so very, very cheap, it comes down to rewarding people's time. And it so happens that for many developers, the product is its own reward.

    Software only represents a slice of any business's operation, and whether OSS is free or cheap makes little difference. However, when software is expensive (think SAP or Oracle), it eats so deeply into the business that little is left for other investment.

    Managers need first to learn that large swathes of the software landscape are now completely in the domain of "as cheap as air", and only foolish people will still pay for something that their competitors get for nothing.

    Managers need secondly to learn that this process keeps on moving. One by one the bastions of commercial software will become commodity items. The businesses with the capacity to be pioneers will always benefit. The rest will follow when the technology curve flattens out and moves into the "general market" and then "late adopter" phase.

    OSS is simply a slice of a standard S-shaped technology curve. It's the same curve that drives Moore's Law, and indeed, one can say that software cost has a half-life. One could even estimate this. Allow me to state "Heironymous' Law" of falling software costs: every 18 months, software products fall in cost by half, eventually reaching effective zero.

    Which is why we can now get databases, office suites, Beowulf clustering software, etc. etc. etc. for the cost of bandwidth.

    Patents, by the way, are a brake on this technology curve, and this is IMHO why those of us who love and feel this curve hate patents so much. Technology wants to be free.

    --
    Ceci n'est pas une signature
  50. Re:My experiance with linux by Anonymous Coward · · Score: 0
  51. But what about free beer? by Anonymous Coward · · Score: 0

    The article doesn't make mention of free beer. It's all about the free beer man...

  52. Re:Open Source is bad for the economy. by Fiveeight · · Score: 1

    From your comment #6286101

    "Why do you think Microsoft wont hire Americans anymore? I know, because stupid open source robots are willinng to code for free!! Why hire anyone when Microsoft can just take the open source code, use it in their closed source products, and no one would ever know because no one sees the code!"

    From your comment #6286101

    "Also Microsoft, I'm assuming this is who the movie wanted to imply it was about, is one of the most honest corperations on the face of the earth, they support affirmative action and have donated millions of computers running billions of dollars worth of the best most well known software. Bill Gates also gives scholarships, gives money to India, Africa, China, Europe, this man should be knighted."

    I'm impressed by your ability to troll from both sides of the MS opinion spectrum

  53. Super by CommieBozo · · Score: 1

    I don't care about open source. I just use what's best, and what's cheapest. If you think about this stuff too much you'll go crazy and/or geeky.

  54. Perhaps... by Tadrith · · Score: 3, Insightful

    ...corporate managers would be more willing to work with things such as open source, when the open source community stops referring to them by childish names.

    While the attitudes represented here on Slashdot assuredly are not indicative of many who contribute to open source, it's silly to think that the attitudes that frequently show themselves here do not get back to these people. Many of them do read sites such as Slashdot, and until the community can manage to present itself in a respectable manner, and in a way that's acceptable to corporate culture, I don't think widespread adoption will take place.

    There's definitely promise in open source, which is why you see companies like IBM and Red Hat attempting to put a polished corporate face that people can associate with on Linux. They're trying to bridge the massive gap between the way corporate managers think, and the way your average Slashdot reader thinks. However, the community has a loud voice... and unfortunately, frequently all that comes out of it is sarcasm and snide comments. These companies can only do so much.

    1. Re:Perhaps... by Allegro · · Score: 1

      Let me get this straight: corporate suits are going to not save money, not have flexibility, not have generally stable software simply because of some attitude that a few geeks on Slashdot have?

      Well, to that I say, "Good riddens!" I don't care if corporate suits have a problem with my attitude. Why should I? They can either stand on the shoulders of giants, or they can choose not to. Either way, I don't care.

      --
      Don't let the lusers get you down.
    2. Re:Perhaps... by Anonymous Coward · · Score: 0

      I'm a self confessed nerd, a geek, a boffin whatever. Me calling a corporate manager a PHB is something he has to live with, he may not see himself like that but I'm sure he prefers "PHB" to "suited fuck".

      And I'm positive that none of the "Get a girlfriend, a shave and a wash! you tree-hugging linux using communist freaks" comments on slashdot are ever posted by corporate managers. PHB's must be far above all that because "They wear suits you know"!

    3. Re:Perhaps... by RatBastard · · Score: 2, Insightful

      The other issue is that businessmen/women don't give a damn about Open Source, save for ownership issues of anything designed in-house. Why? Unless the point of teh company is to develope software, they are not interested in getting at the source code. They are interested in a solution that works and will be supported by a vender of some sort.

      The theology of Open Source is meaningless to them.

      and I tend to agree with them. I'm not aprogrammer. I don't care about the source code. I couldn't find a trojen or back door if the comments in the source code told me it was there. I do care about open formats and standards that allow flexibility in my software chioices (say, using MPG video rather than WMV, or XML rather than that funky crap Word and Excel use).

      --
      Boobies never hurt anyone. - Sherry Glaser.
    4. Re:Perhaps... by transient · · Score: 1
      Agreed. As a manager, I find the attitudes of a lot of Slashdotters to be off-putting. Look, for example, at the synopsis at the top of this page, which equates my profession with a well-known Dilbert character. The message is that I am too stupid to understand the virtues of open source software. This is not an effective technique to win admiration from the people who write your performance evaluations.

      (For the record, my team runs Linux on 85% of our servers.)

      --

      irb(main):001:0>
    5. Re:Perhaps... by Tadrith · · Score: 1

      Nobody said you had to give a damn about them. I was simply responding to the frequently asked question of "Why isn't open source more popular?". It seems to be a hot topic on Slashdot pretty frequently. So, while you might not give a damn, many people do.

      Nobody likes to be disrespected, and people go to great lengths to gain that respect, sometimes at a cost to themselves. In light of that, yes -- many "suits" will choose another route over open source, because that aspect of it is very important. Keep in mind, there are other aspects that contribute to the problem as well... this is merely a single facet.

      Oh, yeah. The word is "riddance", not "riddens".

    6. Re:Perhaps... by Allegro · · Score: 1

      Why would you choose to point towards the attitudes of the Slashdot community, in this case, rather than other issues? I feel quite confident that the Slashdot community's attitudes towards suits has very little to do with Linux's lack of acceptance. At least, I feel that way in light of other issues such as file format compatibility, lack of hardware vendor support, and perceived difficulty in use.

      And thank you for making a big deal over my spelling mistake. How humble of you...

      --
      Don't let the lusers get you down.
  55. OSS superset of FS by dh003i · · Score: 3, Informative
    OSS is not the same thing as FS. There are connections between the two of them, but they are not the same thing.

    At it's most basic level, FS is concerned about the freedom of users. Users should have certain freedoms. See the FSF's Free Software Definition (FSD). The FSF has also published an article describing what they think FS (Free Software) is better than OS (Open Source).

    OSS is more about a development model than user and developer freedoms. The freedoms it ensures to the user and developers are geared towards that development model. See the OSI's Open Source Definition (OSD) (OSD).

    Summarily, OSS is a superset of FS, FS a subset of OSS. Anything that is FS is also OSS; however, many things that are OSS are not FS. The FSD has a stricter definition than does the OSD, thus many licenses that the FSD deems too restrictive are acceptable under the OSD. For example, the OSI considers the APSL (Apple Public Software License) to be OSS, but the FSF does not consider the ASPL to be FS.

    A relevant quote from the FSF's webpage:
    The fundamental difference between the two movements is in their values, their ways of looking at the world. For the Open Source movement, the issue of whether software should be open source is a practical question, not an ethical one. As one person put it, ``Open source is a development methodology; free software is a social movement.'' For the Open Source movement, non-free software is a suboptimal solution. For the Free Software movement, non-free software is a social problem and free software is the solution.
  56. Eh? by cubicledrone · · Score: 1, Interesting

    You actually think PHBs give a flying rabbit-shit what Open Source is?

    Here is the PHB daily priority list:

    1) The Lunch Menu
    2) What's at Blockbuster on Friday
    3) Today's all-day meeting refreshments

    --
    Business isn't willing to pay for products, innovation and careers, so we get brands, mortgage commercials and layoffs.
  57. Re:no by youaredan · · Score: 1

    I guess that's like women, except its never guarenteed you'll understand - in fact you never will... ah hell.

    --
    -Digital Extremist // digitale
  58. (for me), OpenSource != free. by danalien · · Score: 1

    No I haven't read the article yet, I just wanted to express how I see the whole OpenSourceness first before getting tainted.

    Simply put, OpenSource doesn't say anything about that it should be 100% free (or anything like that). Simply says (according to GPL) that with your distribution (if you used any GPL work) you simply have to provide the source code also.

    So, OpenSource is the act of providing the source code to your customers, free from any extra charges, so if they want to custom fit it to their needs they have the avalibility. And if they want to distribute their "custom-fit", they have to give credits where credis are do, by providing the source (as they are/where not the actuall body/organisation/coder whom wrote the first lines of codes of the coreponding program).

    If, people are so generous, that they give you "program" for a $0 fee (for what ever reason; goodwill or what ever) and also provide you with full source code (opensource), don't start label "opensourceness" as "free", because there are other bodies/organisation/coders out there that charge $xxx and also provide their code (that is aswell, in my vocabularry, "OpenSourceness", thought limiting if one can't distribute onse own "custom-fit" based on the acquired code).

    --
    I don't claim I know more than I know, and if you know you know more than I know, then by all means, let me know.
  59. Starbucks coffee tastes like burnt cardboard by Anonymous Coward · · Score: 0

    Full flavored, perhaps, if you enjoy tasting what amounts to what the cup would taste like if you ate it after you were through with the coffee.

    Any thoughts to this e/n rant? I like Bob Newhart, BTW.

    1. Re:Starbucks coffee tastes like burnt cardboard by Anonymous Coward · · Score: 0

      I like you, too.

      BN

  60. Re:The GPL and Open Source are a cancer. by crazyphilman · · Score: 1

    Ha ha ha! Too funny... You forgot "Open source is a VIRUS that will infect all your IP!!!" (You have to imitate the Monkeyboy when you say it, though -- get your face really red, get really sweaty, with the sweaty patches under your arms and the glistening face and bald spot, and run back and forth swinging your arms). ;)

    I keep wondering about that guy; if he keeps up all that running and arm waving, he's going to have a heart attack! He's not exactly a spring chicken... Isn't he worried? Maybe he's pulling a Loman and going for a life insurance payout for his family...

    --
    Farewell! It's been a fine buncha years!
  61. Beyond the Source by Anonymous Coward · · Score: 0

    A new capital investment/business model that's taking the world by storm. It's a more level playing field between corporations and privately held enterprise (purer form of capitalism).

    It no longer has much to do about source code

  62. one additional note by dh003i · · Score: 2, Insightful

    Something I forgot to mention. Despite the fact that both of these groups have slightly different ideologies, in real-world terms, they both agree -- for the most part -- on what licenses are acceptable, which means that individuals from the two movements can and do work together to accomplish common goals (as most of their goals are common).

    It is rather like two different groups of individuals who support the right to choose regarding abortion. One group may support that right because of ideological reasons: they think women should be entitled to that choice. Another group may support that right because of practical reasons: they think that the effects of illegalizing it are harmful. In the vast majority of cases, both groups will agree with one another, and can work together to accomplish a common goal. It is called an incompletely theorized consensus. The Founding Father's had such in regards to their conception of privacy.

  63. That is the correct answer by Anonymous Coward · · Score: 0

    Come on, you groupthinking clowns, realize your failures and dish out propers here.

  64. The Source Te Ching by identity0 · · Score: 1

    Bah, there's so many Matrix/Jedi/Magic references here... Forget all those pop-crap 'reinterpretations', here's the real thing:

    Source Te Ching - The Source and Its Power (by Lao Stallman)

    That which cannot be compiled, is not the True Source.
    That which must be NDA'd is not the Open Source.
    The code is the Source of all things, great and small.

    Ever desireless, one can see the mystery. Ever desiring, one sees the manifestations.
    These two spring from the same source but differ in name;
    this appears as darkness.
    Darkness within darkness.
    The gate to all mystery.

  65. ok by BigBir3d · · Score: 2, Insightful
    Do PHBs really need to read this sort of introduction to get comfortable with the idea of using Linux and other open source software?"

    Do you want your boss to understand what you need?

    In case you didn't notice (which I am assuming you didn't since the question was asked), your boss won't sign off on a huge shift in company policy without understanding the situation. I am talking more than the "blah blah cheaper" or the "blah blah security" arguments.

    Managers respect calm, cool, intellectual evidence. Spitting (side effect of excitement in some geeks), poorly shaven, long-haired, smelly, hippy looking guys, espousing the socialist aspects of open source (that is what it sounds like to most un-informed mgmt types) get nowhere unless they are preaching to the choir.
    1. Re:ok by Anonymous Coward · · Score: 0

      It's called economic redistribution.

      Or not getting the shit kicked out of you in high school for not wearing the right shoes and jeans...

  66. Tree in the woods by Bigby · · Score: 1

    If OSS were developed by someone and no one was there to see them contribute the code, would it still be OSS?

  67. Re:The GPL and Open Source are a cancer. by Poeir · · Score: 1

    Why is it every film of Ballmer has him running and jumping, but somehow, he hasn't lost any weight?

    --
    Sigs are like bumper stickers.
  68. The code in the opening credits was HTML... by BitwizeGHC · · Score: 1

    but on the screens in the movie they used what looked like Java. Even at Evil M$-like Company.

    --
    N4st0r, trixx0r h0bb1tz0rz! Th3y st0l3 0ur pr3c10uzz!
  69. Re:What is open source? by Anonymous Coward · · Score: 0

    Get it right you insensitive clod! Well-cooked apple pie is only eaten fascists, to us lefties open sauce is the only thing that could make such a dish palatable.

  70. Re:Open Source is bad for the economy. by crazyphilman · · Score: 1

    He's got another kinda funny troll elsewhere in this discussion somewhere... He must be in a whimsical mood today. They're pretty good trolls. He almost sounds serious.

    --
    Farewell! It's been a fine buncha years!
  71. Open Source by Anonvmous+Coward · · Score: 2, Insightful

    Open Source: The re-writing of already released software in order to avoid paying for it.

    Man I hope people are in good humor today.

    1. Re:Open Source by Anonymous Coward · · Score: 2, Interesting

      The MS platform is a hell of alot more tainted.

      If you make something good for an MS platform, you'll end up competing with them unless your bought out. Every MS internally started venture (excluding Directx) has failed. MS has a tendency to buy the cleap clones and attempt to rewrite history.

    2. Re:Open Source by ratfynk · · Score: 2, Interesting

      What is open source? It is a natural response to proprietary hardware. The history of pc hardware has driven the move to open source. The real reason open source is common now is that to run a Unix like os on a cheap disposable pc is important to any computer science student.

      Just try to use MS academic licenced compilers and you will understand the difference. With open source you get to see and learn how base c libraries really work. Far better for learning than the hidden binaries necessary for closed source computing.

      Even the Microserfs use open source to learn how things work. Working for Microsoft is like working for the CIA, you are only allowed to see the source segments you are working on.

      --
      OH THE SHAME I fell off the wagon and use sigs again!
  72. I==T3H R0X0R! by Anonymous Coward · · Score: 0
    Firstus Postus, Beeeeeotchae!!!!

    Bow down and worship my multivariate magnificence!






    pleeeeeeeease?!!!

  73. Tux Icon for Opensource by Anonymous Coward · · Score: 0

    Why is thier a Tux icon for Opensource? /me starts a campaign for a whole new opensource icon.

  74. A good example of why... by dh003i · · Score: 1

    The term "Free Software" is better than "Open Source Software". Open Source has one obvious implication: that you can view the source. Free Software can be taken to mean either free as in speech, or free as in beer: at least there's a 50/50 chance someone will get it right off the bat. Aside from that, as the FSF has said, once the user understands "Free Software as in speech, not beer", s/he won't get it wrong again. Not so easy with OSS.

    The FSF is not entirely happy with the term "Free Software", precisely because it's only 50/50. Some other potential names they could use -- e.g., Liberty Software -- are associated with political movements that the FSF does not agree with and are beyond it's scope. Libre Software would be appropriate, but it uses foreign words, which is confusing.

    I suggested to RMS that the FSF use "Freedom Software". However, the FSF had apparently considered that as a superior solution, but decided that they couldn't use it, because Freedom Software is the trademarked name of a company that has nothing to do with Free Software. This is a tragic example of how trademark laws are bad for the public. The public would be done a real service if the FSF could call their software "Freedom Software", but trademark laws prevent it.

    So, if you really value Free Software, you should work on two things: (1) Finding some way to invalidate the trademark on Freedom Software [look through legal case history, if you're a lawyer]; (2) Starting/contributing to an effort to pay Freedom Software to turn over their trademark to the FSF.

    1. Re:A good example of why... by grahamlee · · Score: 1
      Libre Software would be appropriate, but it uses foreign words, which is confusing.

      To Linus Torvalds, the words 'Free' and 'Software' are foreign. Actually, they're foreign to most of the people who work at SuSE, or Mandrake (they're French, so 'Libre Software' would be quite nice), many of the GNUstep community, the people at Red Flag Linux, and so forth. And in a time when many of the Free Software projects are striving for ubiquitous i18n support, is using the odd alien (from the Old French) word such am bad thing?

      Hint for considering which words people will find foreign: the language spoken by most people in the world is Mandarin. English is (I think) fourth, with French (from whence, the word 'libre') being second.

  75. I'd mod you up if I could. by RatBastard · · Score: 2, Insightful

    Mostly because I agree that a lot of open source projects exist for that very reason.

    But I'm also a cynic.

    --
    Boobies never hurt anyone. - Sherry Glaser.
  76. The concept or the community? by phorm · · Score: 2, Insightful

    All IMHO of course...

    The OS concept is basic in the idea that you can view and/or modify (assuming that you have the skills) the functionality of a program being provided to your or your company. In many cases, it also means that the software itself may be free, and will permit personal modificatins, etc.

    The OS community as a whole is a combination of people who fall into one or many categories:
    a) With a goal to improve IT as a whole, by providing software to the global community that is without strangling license terms, hidden bugs/tricks, or other nasties
    b) People that simply want to test their skills, and believe they have something to offer out to the world. The bored, the haxors, those that like to code in their free time.
    c) The code-hippies - "code wants to be free", open-source is like free-love and such individuals tend to be highly anti-capitalism or anti-corporation.

    Whilst I realize that many people may take offense to the "hippy" remark, you must understand that a lot of the reason the hippy era is looked down upon is because corporate culture one. The concept of "sharing information" for the betterment of everyone is something that has been around long before either hippies, coders, or Open Source - but it's something often quite common to all. I see us as a group with slightly radical ideas, but something real to offer that is becoming increasingly valuable as the corporate noose tightens on the world.

    Many projects are (in most ways) free, and are a way of saying to the world, "this is my contribution. Value it, find use in it, and see that there is another way. If you can, take what we have given to you, improve on it, and give it back to the community."

    Truly, I doubt that a roomful of OS geeks could get together and agree wholly on anything, but we could co-exist with the knowledge that at least at some level - we share a common cause and common roots. OS is quite possibly one of the few contenders left to give a little hopefulness to an increasingly corporate world, so let's hope we succeed.

  77. Re:Steve Ballmer is a genius. by crazyphilman · · Score: 1

    My, you're in a whimsical mood today. I know you're trolling, but I don't mind; it's so skillful! I have to appreciate the pure elegance of it. So, I'll play along, just out of respect for your mad skills.

    There's not much to say here, but I'll say this: it's not that I care what happens to the Monkeyboy. It's just that I'm morbidly fascinated by it. The spectacle, the weirdness of it all... It's just so freaky!

    Anyway, trolling aside, I'd like to point something out: how much money he has is immaterial. I'm happy, I've got plenty of money for my needs, and as a result I feel that I'm far richer than he could ever be. Besides, I'm a great lay, and that's something money just can't buy. ;)

    P.S. Bite your tongue! Longhorn! Are you MAD? Go FreeBSD!

    --
    Farewell! It's been a fine buncha years!
  78. Re:The GPL and Open Source are a cancer. by crazyphilman · · Score: 1

    I dunno; it's freaky, isn't it? Maybe it's because he's always out of breath after about twenty seconds, so he never gets to the stage where he'd actually burn fat (they say it takes at least 20 minutes to a half hour to burn up all your blood sugar when you exercise)...

    --
    Farewell! It's been a fine buncha years!
  79. Godwin's Law by Anonymous Coward · · Score: 0

    You forgot to invoke Godwin's Law.

  80. What Is Open Source? by cioxx · · Score: 1

    One word: Medicine

  81. Re:Shared Source is better than open source. by Zeriel · · Score: 1

    Man, what happened? You used to be a, nay, THE classic example of the "well-meaning dimwit" troll.

    Now you're just reaching. Sad how some folks don't know enough to retire when the start going downhill.

    --
    "America has done some terrible things. But I know that Americans don't cheer when innocents die." -Dave Barry
  82. irrelevant by dh003i · · Score: 1

    Irrelevant of his obvious dislike of the FSF -- which I disagree with -- at least he knows the difference between FS and OSS. The original *imbecile* does not know that difference. Worse yet, he posted a top-level comment that will confuse many new users into thinking that FS and OSS are two different names for exactly the same thing.

    1. Re:irrelevant by ichimunki · · Score: 1

      Considering that people like Bruce Perens use the terms "Free Software" and "Open Source" interchangeably, this confusion is probably understandable and likely to be an ongoing problem. Indeed, here is a quote from the preface to Mr. Perens' latest speech: I use "Free Software" and "Open Source" interchangibly. They are both different ways of looking at the same thing, one emphasizing freedom and the other talking more about value to business.

      For my part, I understand what you are saying and prefer the phrase (and ideology of) "Free Software". My first thought when I saw this article headline was "too bad they weren't talking about Free Software".

      --
      I do not have a signature
    2. Re:irrelevant by dh003i · · Score: 1

      I disagree that they are different ways of looking at the same thing. The definition for FS is more narrow than that for OSS. The OSI considers some licenses (like the APSL) to be OSS, which the FSF does not consider to be FS. Thus, in there are some differences in the details of the matter too (though probably 90% of the licenses that are OSS are also FS).

      Loosely speaking, Perens is right. For the most part (e.g., that 90%), they are different ways of looking at the same thing, one emphasizing freedom, the other business value. More strictly speaking, he is wrong.

  83. Re:Steve Ballmer is a genius. by Anonymous Coward · · Score: 0

    Wow, I broke fucko. Go me.

  84. Re:What is open source? by Anonymous Coward · · Score: 0

    That most interesting of human endeavors whereby some people give away the fruit of their labor and get nothing in return.

    Are you sure?

    Linus got GCC.

    RMS got a kernel, and the foundation of Unix utilities.

    The Apache group got a robust, stable webserver, and multiple OSes to run it on.

    They all got the internet. (The internet was founded on open source ideals.)

    With open source, everybody wins.

  85. Takedown... by MsGeek · · Score: 1

    SUCKED. It was a hatchet job.

    Right now the most accurate portrayal of a computer hack is in "Matrix Reloaded," where Trinity uses nmap to exploit the hole in SSH1.

    However, the finest and most entertaining movie about geeks remains "Pirates of Silicon Valley." AOL Time Warner needs to release it on DVD. Soon.

    "Revolution OS" is the most factually accurate movie about geeks. However, it lacks entertainment value, and is clumsily edited, scored and directed. Someone especially fell asleep at the switch during the audio mix...the Philip Glass-clone music is mixed way too loud over everything else. Still, it's important because it tells the Linux story as it is, like it is.

    Pointy-haired Bosses need to see "Revolution OS". It will keep their attention better than a multi-page white paper.

    --
    Knowledge is power. Knowledge shared is power multiplied.
  86. "All About the Benjamins" by Anonymous Coward · · Score: 0

    This process to instill some type of caste/class system within a such a broad representation of society seems a little idiotic. The corporations that have come under the OS wing have done so because it made economic sense, not because of the dot com hype. Linux on wall street went with little publication, yet was "the" largest driving force for enterprise linux.

    A select group of people welding status for social and economic gain has done little but rip this country apart and will likely do the same to Open Source.

    Your talking BS or dot com hype, heh, surprised your not in jail yet.

    "The way a stupid person beats a group of smart people is by making one of them number one."

  87. Yeah, right. by mindstrm · · Score: 1

    I mean, sure, for the biggest and largest contracts, that is true.. but only thet biggest and largest.

    What many people find with open source is that, regardless of the lack of a formal definition of who provides support.. SUPPORT IS THERE.

    It's far easier to get support, meaning, to get help solving your problems with most open source stuff than it is with closed stuff, period.

    Ever had to call microsoft?

    1. Re:Yeah, right. by Cereal+Box · · Score: 1

      It's far easier to get support, meaning, to get help solving your problems with most open source stuff than it is with closed stuff, period.

      Ever had to call microsoft?


      No, because generally any software contract worth its cost will give you a contact, usually the project lead himself. You don't call "big corporation XYZ" if you've got a problem, you talk to "John Smith", the guy who oversaw the development of the software you're shelling out for. I think this is one of the biggest misconceptions OSS advocates have about how closed source projects work.

  88. Against the dark side by Iowaguy · · Score: 1

    Q: Master Yoda, what is the Source?
    A: Hrmm, Mysterious is not the source. The source is all around us. It is found in Apples and the Pc's that render the fishes and the trees. The source is especially strong in the Unix, which is known as the light side of the Source. But beware. Fear, Uncertinity, and Doubt. These are the tools of the Darkside....
    -Iowa

    --
    "He who laughs last, didn't get the joke."-Cap
    1. Re:Against the dark side by Anonymous Coward · · Score: 0

      +7 Hilarious

      Worth a copy and paste if it is under GNU.

  89. Bold claims by stinky+wizzleteats · · Score: 2, Interesting

    From the article:

    Open Source software solutions exist for virtually all types of business applications.

    Don't get me wrong. I am a very big proponent of Open Source software. Not only do I think it is a good idea, I honestly think that it is very good for humanity as a whole. My only problem is that that statement is somewhat misleading.

    While the basic office application suite is just reaching a maturity level where it can be plausibly considered a viable solution, business applications consist of a lot more than that, and often include very specialized industry-specific niche software. A PHB is going to read that statement, look at whoever handed them the article (it must be printed for the PHB to read it, so all this is happening in meatspace), and ask them if there is an open source version of the real estate accounting software they use. Those of us who have seen such software will immediately realize that we are not talking about a speadsheet, nor a Quicken clone, but a very complex and full featured accounting package some oddball company with no competition writes for that particular industry. It will be buggy, bloated, and incredibly expensive, but it is often the only tool to do certain things that particular business needs.

    Furthermore, there are certian generalized types of business software, most notably document management, groupware, and workflow that don't (to my knowledge) have effective open source solutions. (Part of the reason I am risking a troll mod in writing this is to find out that I am wrong, so if you know something I don't, please reply!)

    The way I see it, the Open Source approach to these sorts of problems is to put the problem solver closer to the problem. Rather than pay $80000 to some screwy outfit in Nevada who happens to write the world's only accounting and office managment package for veterinarians, you hook up with the local Linux guru who knows something about PHP, MySQL, etc. and have him develop a database solution. This leverages the flexibility and power of Open Source software and results in a fairer and more responsible arragement between the providers and consumers of technology services.

    If that business model is what we are all about (as Open Source people), don't we need to sell that idea to PHBs?

  90. What is Open Source? by Anonymous Coward · · Score: 0
    A front for Free Software.

    Don't believe me? Then just ask Raymond. It is in his own words!

  91. Re:So.. if you let it go? by mykepredko · · Score: 1

    It will come back, stronger and more faithful than ever?

    myke

  92. Call Hallmark... by mykepredko · · Score: 1

    I can see it now along with this, on the cover of the card, a beautiful elfin face looking longingly into a CRT...

    and when you open card it says, "See why you were a dumb shit for buying Microsoft?"

    myke

  93. Other great topics for Managers by TheLastUser · · Score: 2, Funny

    What is programming?
    How can a cursor be moved across the screen?
    What are computers?

  94. Re:NO by tcopeland · · Score: 2, Insightful

    > Open Source developers have to respect end users

    "Open Source developers" are not a monolithic entity. They are just people. All kinds of folks write open source software - nice people, mean people, nice people who are having a bad day, people with big egos, people who want to help, etc.

    That being the case, there will always be people who respond to questions with "RTFM j00 n00b." And there are others who will respond with "thanks for the feedback, please see question number 12 in the FAQ, does that help?".

    If you're working on a project, you have a choice every time someone posts to your lists/forums/whatever - how will you respond?

  95. Note the promises in the article by jtheory · · Score: 2, Insightful

    This made me squirm a little:
    Open Source software has the following characteristics, some of which are not usually found in legacy commercial software:

    # Control resides with the user
    # Highly stable
    # Proven security
    # End-User input to evolving functionality
    # Excellent quality
    # Highly flexible
    # No or reduced License Fees
    # No vendor lock-in
    # Self-determined upgrade path
    # Can run on less expensive hardware
    # Very cost-effective
    # Freedom of vendor choice
    # Fast development cycles
    # Ongoing evolution.


    Wow, all open source projects have these features? I think it's important to let managers out there understand that there *are* some high-quality OSS projects out there, but it's not nice to just ignore the fact that most OSS work is crap.

    Sure, you can find 300 projects in SourceForge for any given need... but most of them are still in the concept phase, or comprise a few crappy pieces of code that are currently running on a single teenager's home server.

    I just tend to think it doesn't help anyone to present such a one-sided viewpoint.

    --
    There are only 10 types of people: those who understand decimal, those who don't, and, uh, 8 other types I forget.
  96. Hippies (Re:The concept or the community?) by Ricin · · Score: 1

    It's interesting that you mention the "hippy stigma". Today's CEOs are from the hippy age. So are the corporate hawks running the US today. The neocons are former "liberals". And if you think this is a long stretch I got two words: Sonny Bono.

    Typical isn't it. In business and government and surely also in the justice systems it seems that the 60s and early 70s produced quite its opposite in the end. It's not explained as a counter culture because it's those same people (at least for a substantial part it must be) that are in power now. Not all of them of course but many. It can't be explained adequately with coming of age either.

    So maybe this is better put into terms of class and not of culture or zeitgeist. But in every zeit the geist will fall for it. And then the "hippy stigma" is just another stick to wack the dog with. The dog in this case is anything grassroots that appears to be gaining influence. Kneejerk reaction and thus popular amongst the influential and the chumps alike.

    Philosopher's hat off now.

  97. Re:What is open source? by pyrrho · · Score: 1

    really?

    I think it's more about the natural process of commoditization.

    You can't charge 150% markup on Thyme and Sage forever, you know.

    Also, most software engineering takes place for people that use software, not people that sell it. Those people have good reason to share a bedrock of tools.

    But your average whiney capitalist think they ought to collect six figures for software written in 1985 just forever --- that's the fair thing. Oh well, it's a battle, you'll win or lose and right and wrong will have little to do with it.

    --

    -pyrrho

  98. folow the $$$$$$$$ by Anonymous Coward · · Score: 0

    Budgets are meant to be spent. If software doesn't cost anything, it can't come out of a budget. If you don't spend your budget, it won't grow. If your budget won't grow, it shrinks and so on, and so on, and so on.

    Shrinking budgets sound great on paper, but there isn't a manager in world who wants to do next year's work with less money than this year.

  99. GPL by rabidcow · · Score: 1
    > You only have to provide the source code to those who have access to the binary code.

    This is only true if you distribute the source code with the binary.

    > I believe you can even withold the source until it is requested (don't quote me on that, though).

    Yep, but you have to provide the source to anyone who asks for it.

    IANAL, but: (Section 3b of GPL)
    " Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange"
    (emph. mine)


    If you get really literal, there's a possible exception of either the original author or the FSF. (ie, you don't have to give it to the second party ;)
  100. I had thought of that by dh003i · · Score: 1

    However, the US accounts for more software-using individuals than any other nation, to my knowledge.

    Saying Libre Software would be fine for the French division of the FSF. Actually, there is a page Libre Software (Google it). Not for the English division.

    1. Re:I had thought of that by grahamlee · · Score: 1

      I'm not sure I understand your logic. The reason that 'Libre' can't be used is because Americans wouldn't understand it, is what I think you're saying. But RMS requires large number of pages to explain the word 'Free' as in freedom, which is a word used in America. So I don't think it would make many odds :-)

    2. Re:I had thought of that by dh003i · · Score: 1

      Good point. I'll have to ask about that. There must be a reason.

  101. Re:no by kliment · · Score: 1

    yes, it is, and that is a good thing. I think that in a fair community unpaid work should be encouraged and (paradox) paid for. Schemes like citizen's income build upon the idea that one should be free to do paid or unpaid work, in any proportion, and still have a living. Look it up, or check my earlier post on the subject in another discussion.

  102. Toilet seat for a logo? by twoslice · · Score: 1

    Perhaps a little off-topic but... Is it just me or does the opensource logo look like a green toilet seat? - They need a better logo, I mean really, a green toilet seat?

    Check it out...

    http://www.opensource.org/

    --

    From excellent karma to terible karma with a single +5 funny post...
  103. Re:Welcome to the computer age by Psykechan · · Score: 1

    There's always something that needs tweaking or configing or editing. Nothing ever just works.

    This seems to be something that plagues many programs, not just open source ones.

    Problem is, when you have billions of possible hardware combinations running trillions of different application combinations, something will need tweaking.

  104. Don't confuse Open Source with Free Software. by jbn-o · · Score: 1
    well, GPL, being the most prevalent license for OSS, has become nearly synonimous with Open Source for non-technical people. And is that really so bad? If you get the gist of the GPL, then you get the gist of Open Source.

    Not at all. The GNU General Public License was written by the Free Software Foundation for the Free Software movement over a decade before the Open Source movement began. These two movements have different philosophies. Nothing in the pairing of the Open Source movement and the GNU General Public License tells you this. The Free Software movement supports the freedoms to share and modify software and compels you to notice that the benefits the Open Source movement champions come from the freedoms of Free Software (freedoms which the Open Source movement eschews).

  105. Zoltan ! by Anonymous Coward · · Score: 0

    It's power is exceeded only by it's mystery.

  106. Why has this not been implemented anywhere? by dave1g · · Score: 1

    I think all the big Open Source projects should have this.

    Have a feature request link on the website. After the link is pressed a text box to explain the feature is given and paypal/credit card payment system that allows you to list the amount of money (if you wish) to reward the programmer(s) who complete your task.

    This would turn open source development into a market economy, more so than it is now. Big companies can afford to put a OS developer on their payroll to help out and obviously the companies interests would be the programmers first priority, but the smaller end users would now be able to offer $1, $5, $10, $25, $50, $100 (or however much it is worth to them) to who ever comes out with a patch that fixes their problem or adds their requested functionality.

    Others who wish to see this feature/bug fix implemented could contribute to the fund in whatever increment they choose.

    I know 50 bucks doesnâ(TM)t seem like much but some of the bug fixes and features that users request are easy to implement and are just tedious, little, small changes that no one wants to do. This small monetary incentive might speed things up a bit. 50 bucks can also be seen as a 50 dollar coupon on your next computer component purchase. The vast majority of computer components that arenâ(TM)t the top of the line are about 50-200 bucks. CPUs, MB, HDD, CD/DVD R/RW, add in cards, graphics cards, sound cards, scanner, printer, flash memory.

    There are probably some particulars that would need to be worked out if the bug fix/feature is coded by more than one person. But such disputes could go to the project maintainer to divvy out the funds correctly.

    1. Re:Why has this not been implemented anywhere? by MrResistor · · Score: 1

      I had an idea a couple of years ago to start a site that would basically be a clearing house for this sort of thing. Basically, you would go to the site and start a ticket for a particular feature in a particular project and put a few bucks toward it, and later on maybe some other people would add more money to it if it was a feature they wanted. At some point the bounty would be high enough that someone would be interested in doing it.

      My plan was to keep the donated money in an interest-bearing account, and use the dividends to pay for bandwidth and such. If it catches on it should actually be self-sufficient at some point.

      Anyway, as I always say when I present my idea, feel free to steal it. I simply don't have the time to do it myself at the moment, but I'd love to see it happen someday.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
  107. Argh! That's unreadable! by Max+Threshold · · Score: 1
    The writers seem to know their material.

    Why, because they use a lot of meaningless business jargon? No doubt about it, that article is aimed squarely at PHBs.

    Looks like a job for Bullfighter!

  108. Karma to burn, baby by Bugmaster · · Score: 1
    The article says that some of the qualities of open source software are:
    Control resides with the user, Highly stable, Proven security, End-User input to evolving functionality, Excellent quality, Highly flexible
    However, I still haven't found a piece of OSS that lives up to this hype. The UI on all the KDE/Gnome apps is inconsistent and buggy (they have how many clipboard implementations by now ? five ?). The "proven security" works as advertise only if you take extra pains to secure things -- much as it is with commercial software. The software is highly flexible only if you consider "you need to write 10 pages of Perl regexps to make it interoperate with anything else" to be a standard of flexibility. And most OSS is actually unfinished at best, alpha-quality at worst -- I guess that's the "continuous evolution" they were talking about.

    Sure, there are some notable exceptions. Apache, OpenOffice, Postgres, Zope, Mozilla and assorted PHP webapps (though not PHP itself) are reasonably easy to install. Some of these packages, such as OpenOffice, are even relatively easy to configure. However, due to the nature of the underlying OS, none of these packages will ever be as polished as, say, the Windows notepad or Microsoft Office (bloat notwithstanding). Yes, open source has come a long way, but it still has a long way to go if it wants to catch up to commercial products... With the exception, of course, of the packages for which there are no viable commercial analogs, such as Apache & PHP -- they have nothing to catch up to, so they will always be messy in some way.

    --
    >|<*:=
  109. Re:NO by smithmc · · Score: 1

    That being the case, there will always be people who respond to questions with "RTFM j00 n00b."

    That's true, of course. But in my (purely anecdotal and by no means exhaustive) personal experience, there is a greater concentration of such individuals in the free/open source world than in the commercial world. Perhaps one reason for this is that being rude/obnoxious to your potential customers isn't a good way to get them to give you money.

    --
    Downmodding is the refuge of the weak. Don't downmod, make a better argument!
  110. Re:NO by tcopeland · · Score: 1

    > there is a greater concentration of
    > such individuals in the free/open source
    > world

    Yup... I think that relates to the barrier being low for starting an open source project. I mean, all you have to do is find a web site somewhere. Any jerk can do that. To start a company, you usually have to get along with at least a few people :-)

    > being rude/obnoxious to your
    > potential customers isn't a good
    > way to get them to give you money.

    Can't argue with that.

    It's too bad when developers are rude - someone approaching and asking a question is a golden opportunity for improvement - you can answer their question, and then go improve the documentation/code/web site to answer their question without your intervention in the future. All good stuff.

  111. Misconceptions, maybe by mindstrm · · Score: 1

    But having dealt with "support" for a variety of packages.. yes, sometimes you get help.

    The thing is, In all the OSS I've used in a commercial setting (usually corporate), I've never once come across anything where I could not get my answers as fast, or faster, than for any product we had a commercial support agreement for... I guess that's my point.

    So the assertion that "support is not available" Is just not true, although you may not be able to easily define where that support comes from, in practice, it's not an issue.