3 ms·
If you start with GPL stuff (and in my experience most of the really good open source software is GPL), it's very difficult to sell the resulting proprietary pr
by dTal 13y ago
If you start with GPL stuff (and in my experience most of the really good open source software is GPL), it's very difficult to sell the resulting proprietary product, as you must provide the source on request and you cannot prevent it from being shared; thus, anyone can build it themselves (some projects I've seen that use this model deliberately make their build process tricky, I suppose to encourage sales-by-laziness - Apple is the king of this with their essentially-unbuildable releases of Darwin).
No, I rather think the best model is the one where software is treated like a public resource; the knowledge commons. A lot more companies are interested in using software internally than in selling it, and many will already have in-house software developers to build their business-specific systems. It makes a lot of sense for companies to pool their resources on common software problems that they all need to be solved and aren't their core focus.
In a sense, your "base of the pyramid" is something of a special case for this model. Basecamp is software-as-a-service, and Ruby on Rails is utility software designed for the express purpose of creating software-as-a-services. It's to be expected that, as free software gains momentum, the first companies to benefit will be the ones that build applications that need to run on reliable, non-locked-in stacks, because a reliable, non-locked in stack is the first thing that free software needed to build. In the long term, though, I hope that really substantial "user-facing" software gains enough critical mass to become the de-facto standard - for example, Blender or GIMP. In such a scenario, any business that needed an off-the-shelf 3D editor or image editor but also developed in-house software (for example, Pixar) would find it in their interest to patch bugs and generally improve the software that they use, even though they don't sell it.
- Edmond 13y ago>In the long term, though, I hope that really substantial "user-facing" software gains enough critical mass to become the de-facto standard - for example, Blender or GIMP. In such a scenario, any business that needed an off-the-shelf 3D editor or image editor but also developed in-house software (for example, Pixar) would find it in their interest to patch bugs and generally improve the software that they use, even though they don't sell it. I think this is the Achilles heel of free software. It works well for infrastructure software such as OS and middle-ware solutions but doesn't and cannot work well for end-user applications. When you are working on the Linux kernel you only need to concern yourself with the correctness of your solution. When you build end-user applications it is an entirely different concern, you can have the best technical solution and still fail to address users needs. The moment you decide user needs are a priority, your cost is going to go up and more importantly the community strength is likely to falter because a good chunk are going to feel unrepresented. Whether we like to admit it or not, software developers tend to build products for other developers, no matter how much they try the end result will end up appealing more to developers than the general population. This is illustrated by the weak show of Linux on the desktop, for years they've tried but not much has changed. This also happened with smart phones, some might not remember but one of the first truly exciting mobile devices where the Nokia 770 & N800 internet tablets, they were awesome devices but alas were quickly supplanted once the iPhone made its debut. I think this shows that while those devices were awesome (full linux in your pocket, which geek wouldn't love that?)to us as developer they failed to address the general population's needs. The most successful end-user open source application so far is Firefox and that is because Mozilla is basically a quasi business organization and are able to approach developing Firefox like a commercial product.
- zanny 13y ago> Whether we like to admit it or not, software developers tend to build products for other developers, no matter how much they try the end result will end up appealing more to developers than the general population. This is illustrated by the weak show of Linux on the desktop, for years they've tried but not much has changed. I'd like to think if we ever got a sizable enough install base on an open technology, the raw user base would sustain development through bug bounties and feature sponsoring. I still believe the most pure form of software development is someone paying you to fix their problems on a public codebase. They want it fixed, they pay to see it happen, and everyone benefits. The problem, though, is that almost all consumer facing software doesn't see fundage through its user base - Photoshop, for example, is probably one of the most pirated pieces of software in history. It makes money through businesses buying business contracts for tens of thousands or millions of dollars to deploy it in the enterprise because they can't risk the gray space in buying one copy and sharing it around the office. And businesses aren't going to be charitable to fund the development of their tools, even if they would be saving tons of money over paying out corporate contracts to the likes of Adobe.
- e12e 13y ago> If you start with GPL stuff (and in my experience most of the really good open source software is GPL) Much as I prefer the GPL to BSD licences, that sounds odd to me, unless you mean for pretty small values of most. Some best-in-class Free software more or less off the top of my head, that isn't GPL: apache (most everything, but lets stick with httpd and solr) nginx openssh freebsd openbsd openssl ghc go (golang) plan9 PostgreSQL redis riak elasticsearch clang/llvm v8/chrome If you add inn LGPL the list grows, perhaps notably to include erlang and to a certain extent haproxy (I didn't realize licensing had changed, the rationale may be interesting in this context[1]). I guess there are a couple of ways to productize GPL software -- one is the RedHat/Canonical approach: use (rather large) resources on testing and creating a coherent whole, including branding (arguably RedHat does more work here than Canonical -- but Canonical certainly aren't the first to try to value-add on top of Debian). The other way is to sell an appliance of some kind. You could say the kindle and even Android fall under this category (as does haproxy, I guess). > In such a scenario, any business that needed an off-the-shelf 3D editor or image editor but also developed in-house software (for example, Pixar) would find it in their interest to patch bugs and generally improve the software that they use, even though they don't sell it. Absolutely. I think having a base on which to build is crucial for it to be even interesting to release certain software. The effort of releasing a usable version, needs to be as low as possible. Already having an open framework that one can simply "patch into" helps with that, I think. As does having a framework for contributing, and a community/project that will help with testing/merging etc. [1] http://haproxy.1wt.eu/download/1.3/doc/LICENSE http://haproxy.1wt.eu/download/1.3/doc/LICENSE