4 ms·
I was promoting something similar along with a guy named (Quinn?). About three of us here before this thread haha. Anyway, proprietary software dominates in ter
by nickpsecurity 10y ago
I was promoting something similar along with a guy named (Quinn?). About three of us here before this thread haha. Anyway, proprietary software dominates in terms of longevity and profit. FOSS has extra benefits plus lacks specific risks. Seems obvious to me a hybrid is the answer. My first was where people pay for product with source + perpetual license (copyright and patent) for that release + GPL-like rights to fix or extend it for their own purposes. Even distribute those to community of paying users. The final possibility of lock-in or freezing that comes from lack of open distribution is the last straw for open-source people. That needs effective solution.
The alternatives are two things: dual-licensing or just charging for the open-source software. These are fully open-source where they have no risks of proprietary software but risk loosing profit due to freeloaders or knockoffs. The latter option, charging for OSS stuff, threw me as I thought it wasn't allowed per some of the license but an OpenSUSE employee pointed out it's basically what they do. Some others do, too, including one person whose company does custom jobs for other firms plus GPL's anything they make. You basically make it available for people to grab but just keep charging corporations for it anyway. They don't know the difference as they're paying for specific benefits.
What's your thoughts on these OSS options?
EDIT: Wait, yeah it was Quinn with Fair Source. I've been too busy to get back to him but I see all of us having a more extended discussion on these things in future when things stabilize for me. :)
- chipotle_coyote 10y agoMy first was where people pay for product with source + perpetual license (copyright and patent) for that release + GPL-like rights to fix or extend it for their own purposes. Even distribute those to community of paying users. Interestingly enough, similar models seemed to be more common back in the dark ages of computing before terms like Open Source and Free Software were really a thing, particularly on minicomputers and mainframes. It made its way to the "microcomputer" world in more limited fashion, then sort of slowly died out. But I think there may still be something to the notion of a license that, while not remotely meeting the definition of "free software," still gives you access to the source. I'll be honest, though; I think FOSS advocates have a tendency to (perhaps unconsciously) downplay how important "free as in beer" has been for the adoption of a lot of major software projects. An internet in which Apache, MySQL, PHP, and other major free software projects were released with commercial "source included" licenses would probably look very different. I have my own thoughts about RethinkDB's failure as a commercial entity, but despite having actually been inside, I have pretty limited insider knowledge. Perhaps we should have been trying to push an "enterprise edition" with guaranteed support much earlier, following the "charging for OSS stuff" line you mentioned; as others have said, maybe we just didn't have enough avenues through which to give us money. (It's hard not to notice that MariaDB's .com site is essentially page after page of ways to give them money, for instance.)
- nickpsecurity 10y agoThe Burroughs MCP came with source with users allowed to submit updates to them for redistribution. So, the first, great mainframe for business operated under shared-source license. It became a multi-billion dollar company. They closed it off and pulled all kinds of schemes eventually. Now called Unisys. I think a combo of paid with source and closed-source extensions can still get lots of success. We're already seeing it with enterprise editions for features that basically only enterprises use. That keeps them from crippling the main, OSS product which costs less. I also envision giving free licenses to people that contribute lots of code, docs, testing, etc. One way is to simply not charge businesses below a certain revenue amount or only to charge a support fee tied to cost of delivering support. As they grow, so does the software house like in the royalty model.
- tomcam 10y agoI just visited mariadb.com and the front page is all about open source. A free download button is 1 click away. Did not get the feeling of a hard sell at all.
- m_mueller 10y agoI'm curious on what you'd think about my sister comment since you have already been in this position.
- bsder 10y ago> Anyway, proprietary software dominates in terms of longevity and profit. Profit? Sure. Longevity? Not even close. Things like the Spice3 circuit simulator and the Magic VLSI editor can continue to exist and run 30+ years later solely because they are open source.
- nickpsecurity 10y agoMany companies and their enterprise products go back decades with oldest being from 60's. Those are still updated and sold due to lockin. In general case, your point is probably true given natural advantage of open source plus how market kills off so many IT firms.
- flukus 10y agoA lot of OSS software goes back nearly as far, emacs is 40 this year.
- nickpsecurity 10y agoDidnt know it was that old. Still younger than MCP (1961) which Unisys still sells for tens to hundreds of millions a year. Proprietary has record so far if it's old and still supported. Quite a few of them in legacy mode.
- flukus 10y agoWatch out for survivor bias. For every old but still supported platform I'm sure there are dozens that aren't.
- nickpsecurity 10y agoRemember the original comment you responded to agrees that OSS wins here mostly but proprietary software can last a long time. And the oldest so far look proprietary. Survivor bias doesn't change that claim.
- 10y ago
- sqs 10y agoI am the Quinn you mentioned. :) Would love to chat whenever you want. For other folks reading this, the license he is referring to is Fair Source at https://fair.io/ https://fair.io/.