(no title)
Radim | 1 year ago
Sounds harsh, but this is the correct stance.
The free labour you provide is not only "your loss". There are second order effects: you effectively make it harder for others to compete with said commercial entity.
This includes salaried employees of competing companies whose wages you effectively press down. And even other volunteers and non-profits, because defending and sustaining their project in face of "free inputs, for-profit outputs" competition is that much harder. Community projects die because of this.
"Working for free for a commercial entity" is just a bad idea all around. You exploit yourself (whatever, your choice, you may be getting other kicks out of it) and harm others.
romwell|1 year ago
...which, according to you, is a "bad idea all around", since you exploit yourself and harm others.
So, why are you acting against your morals and judgement?
salawat|1 year ago
The town drunk telling you to hand the barkeep your keys does not detract from the validity of their point. Try to approach things from the strongest avenue possible, otherwise things devolve into guttersniping.
And the point is, at some point, you have to get it out there somewhere in order for it to have been said. The only concern I have with the points being made here; is the paradox of FLOSS. We must have a public, free and in the public trust corpus of software. Locking everything behind for profits just leads to computing definitely being inaccessible to most everyone. Yet look at all the value extraction bootstrapped on FLOSS stacks where companies get bootstrapped around the composition of a few primitives; but inevitably hooked by the caste of management/MBA types, or utilized as social engineering lever by governments. See social media, car manufacturers, IaaS now, finance companies, banks, etc ...
It is a most concerning trend.
koolba|1 year ago