News for hackers. Stuff that matters.
Re:How to Pay Professional Maintainers by jka on Monday March 21, 2022 @01:39PM (#30757256)
Interesting - so, to reinterpret: are you saying that one of the significant changes that open source brought about has been to remove purchasing approval barriers for software usage?

...and that we're stuck in a local minima where we now have to get over other, similar approval barriers to send money back towards open source projects? (in the case of projects that accept funding, at least)

(it's possible I've misinterpreted; and, for what it's worth, I think there are other reasons that FOSS has succeeded in addition to what you say - but I like that way of looking at the current landscape)

Re:How to Pay Professional Maintainers by hinkley on Monday March 21, 2022 @02:35PM (#30757945)
In a nutshell, yes.

I observed a number of people say one thing in a group setting but would confess to other things off the record. The purse string issue was high for a lot of people, but as you say that wasn't the only motivation.

I think too that we oversold the Enlightened Self Interest value to the company in open sourcing internal tools. People worked hard on code that they didn't want to have to write again somewhere else, especially not several times. My current and future job satisfaction are elevated by convincing my bosses to free the code, the Greater Good is also improved by doing so. Nothing makes me want to leave like feeling trapped, and any work I do that has value past my expiration date is a big part of feeling like being here still is a choice.

But I think only a few companies ever enjoyed the fruits of that effort to the degree that we were all telling them they would. Sun Microsystems in particular. But the industry benefited enormously, so history will probably be fairly kind.

Re:How to Pay Professional Maintainers by JonChesterfield on Monday March 21, 2022 @03:22PM (#30758539)
It is _really_ annoying to write the same code repeatedly because the last time was inside some other company, especially when there's no plausible IP involved.
Re:How to Pay Professional Maintainers by hinkley on Monday March 21, 2022 @03:33PM (#30758658)
Especially when you make half of the same mistakes every time. No argument here.
Re:How to Pay Professional Maintainers by xxpor on Monday March 21, 2022 @03:04PM (#30758302)
The funny thing is, every eCommerce site already knows this at least implicitly. We've all heard the "every X ms of additional latency on the site reduces our conversion rate Y bps". Adding friction to anything means it's much less likely to get done.

Even for commercial software, if it were easy to purchase, I'd still have to figure out how to make sure we comply with the licensing, get the key into the server, figure out how to deploy it (and not be able to inspect the software to see how it works if I need to).

Or I can just go to github, make sure it has an acceptable license, and run import-from-pypy foobar==1.0.

Re:How to Pay Professional Maintainers by hinkley on Monday March 21, 2022 @03:36PM (#30758696)
I don't think Jetbrains would be where they are today if not for personal license that grants the right no use the software on as many machines as I like. When it was introduced it cost just slightly more than 3 technical books, and I knew a couple of people who used that math to convince others to switch to Jetbrains.

That license is worded specifically for me to use my private copy at work without exposing my employer to liability.

It's surprising to me that more organizations haven't followed suit. But many of these tools run either on the server or on a CI/CD machine so I'm not sure how you'd work that.

Re:How to Pay Professional Maintainers by a_e_k on Monday March 21, 2022 @06:48PM (#30760755)
This is one of the things that sold me on the Affinity graphics suite. Their license [0] works the same way for purchases by private individuals.

[0] https://affinity.serif.com/en-us/licence/