I work on a few Open Source libraries and they're used by companies that make a lot of money, and people often regard me as a mug for doing the hard work for free so that other people can make lots of money. The argument I give in response is that from an economic perspective, you can only make money from a unique advantage, and since Open Source can be used by anyone, it's not giving anyone a unique advantage. I'd p…
Is It Even Worth Working on FOSS Anymore?
91–100 of 284 posts
Re: Is It Even Worth Working on FOSS Anymore?
#92The reasons you write open-source code: - training purposes to better yourself - as a showcase or to build up your reputation to get hired - because you have a niche need in your personal life that no one else already solved None of those reasons are invalidated by big corporations using open-source without paying back.
The original reason may not be invalidated. But as a continuous activity, over years, what exactly is in it for maintainers to get up in the morning and trade their remaining lease on life for value to be consumed by rich leeches?
The fact that you consider users to be “leeches” means you’re missing the point of open source.
Re: Is It Even Worth Working on FOSS Anymore?
#93Log4j vulnerability is mentioned. But is proprietary software more secure than FOSS?
It's not, but it's not what the author is talking about. He's mostly talking that FOSS is a thankless job creating artifacts that will get appropriated by some greedy corporation.
Re: Is It Even Worth Working on FOSS Anymore?
#94Re: Is It Even Worth Working on FOSS Anymore?
#95* modifiable and fork-able code
* free for non-commercial use
* and payment plans defined in code for commercial use.
I'm working on it at github.com/openfare
Re: Is It Even Worth Working on FOSS Anymore?
#96Earlier quoted context omitted.
It's not, but it's not what the author is talking about. He's mostly talking that FOSS is a thankless job creating artifacts that will get appropriated by some greedy corporation.
That’s not what “appropriated” means.
Re: Is It Even Worth Working on FOSS Anymore?
#97Although I agree with many of the sources of frustration mentioned in the article, there is a way: For most software projects, there should be a way to buy a commercial support license. For many, such a license should be required for use in any org which is over X employees. Even if not enforced, this way a conscientious dev can justify for paying for the license. In addition, for some of the deeper "plumbing" projec…
> As an open source coder, I theoretically love the above The above is not open source, it's a pretty common free (gratis) for limited use, paid for other use commercial/proprietary license of the type tons of non-open-source software uses. (E.g., Visual Studio.)
In the case where a support contract is available, but not required, it is no less free than any other free software, but there is at least a chance that it might be bankrolled, as well as the projection that this is a professional project.
Even where the support is required, it is my understanding of RHS that that won't impede on the title free, since the usage is not what you are paying for. But there we are quibbling semantics ;)
Re: Is It Even Worth Working on FOSS Anymore?
#98It's always been this way. You shouldn't enter open source expecting accolades or deference. It's awful the way log4j is being treated. I just don't think anything has changed.
> It's awful the way log4j is being treated. Sadly, that's the way all FLOSS gets treated. I saw this exact same sentence when heartbleed came out with just the project name changed. I don't think that anti-commercialisation clauses in the license will fix anything, though.
Re: Is It Even Worth Working on FOSS Anymore?
#99Although I agree with many of the sources of frustration mentioned in the article, there is a way: For most software projects, there should be a way to buy a commercial support license. For many, such a license should be required for use in any org which is over X employees. Even if not enforced, this way a conscientious dev can justify for paying for the license. In addition, for some of the deeper "plumbing" projec…
I'm working on precisely this problem. My current idea involves payment plans defined in code. See: github.com/openfare/openfare
At least promise, if but a dull glimmer of hope...