4 ms·
> Yes, it's pretty terrible if consenting adults choose to pay for software, isn't it? The thing I zero in on here is that I have literally zero problems payin
by Conan_Kudo 8y ago
> Yes, it's pretty terrible if consenting adults choose to pay for software, isn't it?
The thing I zero in on here is that I have literally zero problems paying for software. But I am wary of purchasing software that I don't get the rights to build, modify, and contribute to.
My worry with software like this is that vendors come and go, and people get their workflows destroyed because the software can't be "saved" when the business is gone (yes, when, not if! always plan for that "exit" that ruins people because the products are gone).
Would I prefer the software to be FOSS? Absolutely. I am also absolutely willing to pay for FOSS, and a good number of Linux users are too.
I'm even willing to take open-core style models if it means there's some FOSS code release, as much as I don't like the model.
I use a mixture of FOSS and proprietary software all the time, not because I want to, but because I _must_.
And in my workplace, FOSS solutions (even ones we pay for) are infinitely preferred over proprietary ones. Desktop Linux support is a must, as well.
- glangdale 8y agoAgreed on most of these points. But I've been on both sides of this transaction, on both sides of the proprietary/FOSS fence (to oversimplify and abstract the difference between Free and Open Source). From experience it is hard to get people to pay for FOSS; my hat is off to those who can manage it. I do think that vendors should have to put things into some form of shared-source or open-source escrow (possibly shared as they might not have IP rights to open source everything they've done) with a kind of 'dead mans switch' arrangement (i.e. you walk away without updating or responding to bug fix requests, you trigger escrow). I'm perennially concerned that the fundamentalist attitude to proprietary software is suppressing innovation in some areas: especially complex desktop software where there is (a) a heavy requirement for the kind of tedious UI work that FOSS projects clearly don't bother to do and (b) where most or all of the product is "right there in the code" (i.e. once you have Photoshop, you can go to town and edit stuff, and you're not really all that dependent on having access to some other product or service which can be monetized). The attitude reaches its most extreme in software tools. Best expressed by Andy Gocke with his great tweet: https://twitter.com/andygocke/status/1017509689695715328 https://twitter.com/andygocke/status/1017509689695715328 'Developer tools seemed like a good industry to be in, "sell shovels in the gold rush" and all, but it turns out developers prefer to dig for gold with their teeth.'