Slashdot Mirror


Why is OSS Commercial Software So Expensive?

An anonymous reader asks: "Our startup honestly wanted to use OSS products. We do not want to spend time for any OSS bug fixing so our main requirement was -official support for all OSS products-. We thought were prepared to pay the price for OSS products, but then we got a price sticker shock. Now behold: QT is $3300 per seat. We have dropped the development and rewrote everything to C# (MSVS 2005 is ~$700). Embedded Linux from a reputable RT vendor is $25,000 per 5 seats per year. We needed only 3 seats. We had to buy 5 nevertheless. The support was bad. We will go for VxWorks or WinCE in our next product. Red Hat Linux WS is $299. An OEM version of Windows XP Pro is ~$140. A Cygwin commercial license will cost tens of thousands of dollars and is only available for large shops. We need 5 seats. Windows Unix services are free. After all, we have decided that the survival of our business is more important for us then 'do-good' ideas. Except for that embedded Linux (slated for WinCE or VxWorks substitution), we are not OSS shop anymore." Why are commercial ports of OSS software so expensive, and what would need to happen before they could be competitive in the future?

15 of 718 comments (clear)

  1. Profit! by riversky · · Score: 3, Informative

    Hire people to make the software (even open source) = Wages to pay

    Hire people to make the software but not pay them = slavery

    Charge more for the product than the wages you pay = PROFIT

    Ok that was way too simple but the bottom line is no one ever said OSS was non-profit or even small profit. In fact by driving down costs these providers can get richer than with proprietary software. The model is buy low and sell high. Economics 101

  2. Support by radish · · Score: 5, Informative

    But you say you want support, that's why you're paying. Hate to break it to you, but an OEM license of XP doesn't buy you any useful support. Neither does a $700 VS license. Microsoft, like everyone else, charges for support contracts.

    --

    ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

    1. Re:Support by swillden · · Score: 4, Informative

      The only way that they can charge more for the "commercial" version AND enforce their right to limit how you use the software is for them to build a completely proprietary project that runs on Linux, then they can license their complete, compiled (with or without source), and wholy owned product however they chose, but if they choose to license under the GPL then they cannot impose the use restrictions.

      Nonsense.

      Qt is licensed under two licenses: The GPL and Trolltech's commercial development license.

      If you use the GPL version, which you acquire from wherever you like, then your application must also be licensed under the GPL, or you have no legal right to distributed it. Technically, you had no legal right to create it, except by accepting the terms of the GPL, because your application is a derived work and creation of derived works is reserved to the copyright holder.

      If you buy the commercial license, you can sell your software as closed source, and you can redistribute the run-time files that Trolltech provides you, or that you build from the copy of the code that Trolltech provides you.

      Code which was originally written under the GPL is not eligible for integration into a work under the commercial license. Not because Trolltech is adding requirements to the GPL, but because Trolltech's commercial license excludes such software from being linked to and distributed with their commercial version of Qt. You can't do it under the commercial license, and you obviously can't do it under the GPL.

      There's no weird copyright theory here, just a couple of different licenses.

      In practice, of course, lots of people start commercial Qt projects prior to purchasing development licenses. I've never heard of Trolltech making any attempt at all to curb this, beyond simply saying that it's not permitted.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  3. It's the support costs. by SarekOfVulcan · · Score: 5, Informative

    How much support do you get from Red Hat for your $299?

    How much from Microsoft for your $140?

  4. Win XP Pro OEm - support? by ahg · · Score: 4, Informative

    Red Hat Linux WS is $299. An OEM version of Windows XP Pro is ~$140.

    And the OEM version of Windows XP Pro is supported by whom?

    I don't know what support Red Hat provides with the $299 version but I know supposrt is primarily what you're paying for or everyone would be using Fedora Core.. Please compare apples to apples - last I heard OEM versions including zero vendor support.

    --

    --Aaron Greenberg

  5. Um... You're *not* paying for the software. by Colin+Smith · · Score: 4, Informative

    Pretty clearly. That bit's available for free.

    You're paying for official support and services. Presumably 24/7 telephone, onsite if necessary. You're paying for people and their expertise not software.

    However, there is a good point. Support is expensive, there's a market out there for lower cost support services.

    --
    Deleted
  6. The answer is in the question... by Noryungi · · Score: 3, Informative
    To wit:

    We do not want to spend time for any OSS bug fixing so our main requirement was -official support for all OSS products-


    Simple solutions:
    1. Make sure your programmers know OSS (Linux or otherwise) inside and out.
    2. Do not buy that support, since your programmers already know how to support themselves, fix bugs and/or know enough to select stable versions of OSS tools, instead of relying on the latest-and-greatest (and buggy) tools from a vendor.


    The same thing happened to me in my last job, a mixed Sun/Linux shop: people complaining about the price of Linux. Why? Because (a) only SuSE Linux was approved for a certain tool, and that tool was considered as critical by the company and (b) because company's policies and bean counters demanded official support from a reputable vendor for everything that was bought. The result? Thousands of Euros spent on buying expensive, gold-plated, 24/7 support contracts. That were almost never used, since both the programming and sysadmin teams had plenty of experience using Linux servers.

    Which makes perfect sense really: Sun support is sometimes cheaper than some Linux vendors, because Sun understands that software support also means hardware lock-in. Microsoft can be cheaper than Linux because, let's face it, all the OEM Windows installed on brand-new computers subsidize the dev tools (C# and Visual what-have-you) while support is essential to the survival of many Linux distributions. Heck, giving the software away for free and selling support contracts is the entire business plan of many Linux distributors! Also, Microsoft understands that, if you, as a developer, buy Visual Thingamajig 2006, you are locked into their platforms, and so are your clients. And that means more money, in the long run, for Microsoft. Why do you think they have recently started to offer programming tools for free? Not out of the goodness of their hearts, that's for sure.

    So, Linux, cheaper? Only if you solid in-house experience. I have also seen companies replacing hundreds of Sun and Windows 2000 R&D workstations by Linux/AMD machines. Why? The official reason was: "Linux is cheaper and good enough to provide the 90% functionalities we need, AMD is cheaper AND more powerful than SPARC CPUs, and everyone here likes (and knows) UNIX systems better anyway"... And that was the VP of R&D speaking.

    So, back to the point above: Linux is cheaper... as long as you have enough experience in-house not to need expensive support contracts.
    --
    The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
  7. Apples vs Oranges by swillden · · Score: 4, Informative

    I think a big part of the problem is that you're comparing different things and wondering why they have different prices.

    Qt vs C#: Sure, C# is cheaper, but the price you quoted for Qt is for triple-platform licenses, and C# doesn't get you that much cross-platform support. Yes, Mono gives you support for other platforms, but it differs in many respects from the Windows version, whereas Qt is very consistent across all of them. Documentation and support for Qt is vastly better than the comparable C# support for non-Windows environments, (and somewhat better than for Windows as well).

    Red Hat vs XP: Red Hat contains far more functionality than XP. Depending on exactly what you're doing, you very likely have to buy additional software for XP. Also, how much support does that $140 XP license get you? Assistance with installation, and that's about it. Red Hat provides a lot more, and it costs a lot more. If you don't think you'll need the extra support, then don't buy it, and Red Hat will be a lot cheaper than XP.

    RT Linux vs WinCE/VxWorks: I can't argue here, not at the prices you quoted, and since you said you got lousy support from the Linux vendor (who was it, BTW?). Perhaps you just needed a different vendor? How about Wind River (makers of VxWorks, for those who don't know).

    Cygwin vs Windows Services for Unix: Depending on what you need, SFU may be fine. As long as you're just using the stuff provided by Microsoft, SFU is pretty good. If you want to be able to download any random Linux/Unix package off the net and have good odds that it will build and run, though, forget it, SFU is completely inadequate while Cygwin will do a good job. Note also that SFU comes with no support, unlike that commercial Cygwin.

    In nearly all cases, I think the core issue is that the prices quoted for OSS support (a) buy you better support than what you'll get in the closed-source case, (b) give you more in functionality, flexibility, or both and (c) are really intended for bigger companies who are less strapped for cash and who have a bigger need of the security blanket the support contracts provide.

    Your company would probably have been better off skipping the support contracts, using the software for no cost, and putting the cash aside to pay an independent consultant or two in case you get in a jam. You can get extremely high-quality support for most OSS for small consulting fees, just by hopping onto the project mailing list, identifying a handful of heavy contributors who know the area you're concerned with, and then privately offering them money for their time.

    Of course, if your management is too uptight to take that approach, and too tight to buy the OSS support, you should go with the closed-source offerings -- and then keep your fingers crossed that you don't have to rely on Microsoft's support. Wind River's support is good, in my experience, but the rest of the stuff you mentioned is from Microsoft.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  8. Re:Not a Good Business Model for Enterprise by djcinsb · · Score: 5, Informative

    The $140 (for XP Pro) is the cost of the OS without other software. Red Hat comes with a compiler suite and a lot of other useful items, so the direct comparison of the costs of the packages is not really a valid measure.

    --
    A signature always reveals a man's character - and sometimes even his name. -- Evan Esar
  9. Re:Some Theories... by swillden · · Score: 4, Informative

    If he did submit a bug and has an open case with Microsoft for it, it is free. Bugs, hotfixes and licensing cases are (and always have been) free.

    Admittedly it's been a few years since I dealt much with MS software, but back around 2000 or so, I found some bugs in VC++ and it cost us $199 per incident to report them. I guess they called it "support" because an MS engineer looked at the problem for a while before deciding it was a bug, but it still seemed like paying money to report bugs to me.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  10. Re:Not a Good Business Model for Enterprise by TheRaven64 · · Score: 4, Informative
    The depends on excellent documentation which isn't enforced in the open source community.

    That depends on the project. In OpenBSD, for example, you are not allowed to commit any code without also committing a corresponding update to the documentation (and your code must be commented according to the OpenBSD KNF guidelines; see man style for more information). Other projects have less strict commit rules.

    --
    I am TheRaven on Soylent News
  11. Re:Commercial versions vs. "based on" by Pharmboy · · Score: 3, Informative

    Inventory management, purchase order, customer record keeping, invoicing, for a company that needs more than 5 seats, but less than 50. Very few users accessing, but ungodly amount of records added daily. 30k+ P.O.s per year alone. (We have very efficient employees) Most software available on FOSS is for individuals, or large corps are writting their own, or you go SAP, etc. and end up paying $100k for a complete solution when you only have 15 people accessing the data. AND it wouldn't do what my current software does, so I would have to pay a programmer to modify stuff.

    Or I can buy cheap Dell computers and about $1000 to $3000 worth of Sage/Peachtree products which suck but get the job done. I even have to pay more for Dell's without Windows. It was a most frustrating time, and no matter how much I wanted to migrate completely over to FOSS, it is pointless if it costs more and does less.

    We still use Linux on all servers, and when the market has products that are cost effective and work for us, we will migrate, but it doesn't look like it will happen soon. I have talked to several people at companies that make software we DO like, and they say they will never port over to Linux. Ever.

    --
    Tequila: It's not just for breakfast anymore!
  12. Re:Not a Good Business Model for Enterprise by skiflyer · · Score: 5, Informative
    I don't really buy that argument, though... lots of people download closed source software without paying. The ones that need support, or want to support the company for whatever reason, are the ones that pay. At this point, OSS just doesn't have the user base it needs to make cheaper prices profitable, but that's not because of people who download it for free. It's because the ones who need support for it aren't very plentiful at the moment.

    Not the kind of stuff this guy is talking about though. Personally I think the problem is he's comparing apples to oranges... I don't have numbers, and I'm not going to go get them, but let me point out a few of the obvious flaws in the summary IMO.
    • RHE to WinXP OEM: Uh, no... Ubuntu to WinXP OEM, RHE to Win2k3 Server
    • QT to MSVS2005: Why not go GTK+ vs. C# Express, both free
    • Embedded Linux ... that's about volume, if you're embedding linux you should be saving a small fortune per appliance vs. putting WinCE on each of them, but yeah, the development aint cheap.
    • Cygwin commercial vs. Windows Unix tools, I think you're mis-understanding what each of those can do.
    Right tool for the job, sometimes it's OSS, sometimes it's not... but the above post is like me complaining about the cost of steel vs. plastic because a caterpillar bulldozer is pricier than my nephew's sand bucket.
  13. Re:He required support by killjoe · · Score: 4, Informative

    So is it your point that no human being can ever buy support for any other open source toolkit other then QT?

    He says that QT costs too much so we goes to VS for around 700 dollars. Does that 700 dollars include support? No it does not. He just threw that out because he is a troll. He is comparing the cost of QT + support to VS without support and picking a solution that only works on windows. C# + GTK is available for free from mono which he also completely ignores.

    The guy decides to drop QT because it costs more and moves to C# without once considering java with swing or swt or anything else? He never considers Mono and goes directly to paying for VS while not buying support from MS.

    The guy is either an idiot, shill, astro turfer or a troll.

    --
    evil is as evil does
  14. Re:Not a Good Business Model for Enterprise by mabhatter654 · · Score: 4, Informative
    excellent example of this... the OS version RH WS versus Window XP. He claims RH WS expensive at $299 while windows is $140 OEM. Read that again. RH is offically supported for so many instance calls per year/term etc.. and if you find a bug they will write it down and may actually fix it... just for you! For 5 seats that's a steal. Compare to MS windows, for starters that $140 price does not entitle you to call Microsoft for any problem! There is NO support for OEM, you must call who you bought it from. The "supported" version is $299 as well... but that still doesn't entitle you to call for support... you have to pay per call for that as well. For 5 seats of windows you're not even a bug on the windscreen.

    As far as the other products he mentioned, they are buying commercial licenses without the usual "GPL only" restrictions as well as support. These are companies that will actually ANSWER your calls and fix problems you find, not just take your money and point you to a website. Remember, MS Visual studio, C#, CE tools may be cheap for price, but come with NO SUPPORT!!! NONE! if you want to actually call somebody, you have to pay per call/hour/service additional. The cost for most commercial products is only to legally USE them. not get help!

    Perhaps this company didn't need quite so many support options, it seems a little silly to purchase the "deluxe" versions for such a small shop. But I'd give them credit for trying and helping out by paying!