upvote
I reckon we’re going to see more proprietary software over the next year.

Gone are the days of commercial organisations using OSS as a marketing tactic to gain a base they later monetise. It worked, it was a tactic and no one really liked it.

Your options will be:

a) community led OSS - like Apache projects, CNCF projects, etc

b) some dudes weekend OSS project

c) commercial vendor, likely proprietary or at best ‘source available’

reply
I disagree. My agents are godlike when I ask them to operate software whose previous version's source is in their training data, and pretty confused when I ask them to operate something proprietary. I wouldn't even use proprietary software if the vendor was paying me to do so (unless they were paying me quite a lot) because there's just so much extra friction around it.

The ideal future of software is not as a product or a service but merely as a tool, used by people with a problem to solve that has nothing to do with selling the tool.

reply
I reckon we’ll see the opposite.

This is the first time “open source” has meant anything other than “probably free” to the average person.

I constantly hear people complain about UIs. You know who probably makes a great UI for non-technical retirees? A non-technical retiree. They’ll probably start from forking an OSS project, though.

I think the really clever folks will move up to building vim/emacs/Firefox esque apps that are heavily scriptable, and your weekend OSS projects will be done by non-technical folks who just want something really specific.

reply
> I constantly hear people complain about UIs. You know who probably makes a great UI for non-technical retirees? A non-technical retiree. They’ll probably start from forking an OSS project, though.

You know what makes a great UI for non-technical people? Codex or Claude.

GUIs were a response to the limited resources available on old computers. And, as we're increasingly finding out, text is FINE. People like Teh Pretty(tm), but they'll take plain text if it solves their problem.

But, congratulations, you DID identify the primary bottleneck--customer support. And, no, I am NOT going to be unpaid customer support for non-technical people. Bleah! Get back to me when Claude/Codex don't suck for that.

reply
some dude coding with 5 max claude accounts gets very far these days
reply
Irony: the number of developers who rely upon other people's open source to develop commercial software or services.

Once upon a time, people payed hundreds or thousands of dollars to acquire software development tools. Even those who programmed as a hobby would have to spend a fair bit of money if they wanted to grow beyond interpreted BASIC.

I'm not claiming the current situation is ideal, but open source has given us much more freedom to program.

reply
I work a job for my money that isn't developing and haven't yet developed something worth enough to others to consider making money that way. If I did, I would consider a finite sum (e.g. kickstart) then release the code. I see software/digital goods as only scarce until they are released. So their value plummets to $0, its only nature defying legal structures that make it otherwise.
reply
Many open-source projects are made for the author's needs, and the author is not interested in implementing feature requests they don't need.

Sending no-strings-attached donations to the person instead of targeted fundraising of the project is just a disservice if you're expecting maintenance, more harm than good.

reply
For maintainers who are being flooded with low-value PRs, maybe they should put up a PR paywall.

PR coming from an individual? Make the price low but not zero and experiment with the price until the PR rate is manageable.

PR coming from a company? Charge your regular rate.

reply
I'd be more likely to participate in something like that if instead of collecting the money, the maintainer is just requiring that I donate it to the EFF or something like that.

Money as proof of this-guy-actually-cares isn't an awful idea but you gotta be careful to not become a parasite.

reply
I don't think of open source software as a way for me to make money, I think of it as a way for me to prevent other people from making money.

An open source project management software nips at JIRA's profit margins. OSM loosens google maps' stranglehold. The swath of FOSS crms delegitimizes Salesforce's per-seat cost. Most recent example is open weight LLMs driving a spike of fear deep into the heart of the current lynchpin of the American economy.

MIT license was a mistake. We tried to play by the rules of capitalists and the obvious happened: the capitalists exploited us. "Thanks for the free labor! By the way, we don't hire people that don't have FOSS commits on their resume." Google and Facebook, last I checked, forbid the inclusion of GPL3 code in their projects. Great! Let's make more GPL3 copies of their software so nobody has to give them money anymore.

reply
I mostly agree, but I don't think that's quite it either. For me, OSS is neither a way for me to make money, nor a way to prevent other people from making money. The latter is closer, but it's not other people making money off of what I create that bothers me, it's that users have to pay someone else in order to use what I created.

I think of OSS as a way to get value into the hands of users and for them to not have to pay someone else for it. I honestly wouldn't be too bothered if they had to pay me, but I relinquish that payment because not paying me means more users and more use, and I have the privilege of a decently paying tech job, so for my personal cost/benefit analysis the free software wins. (And yes, I default to GPL not MIT/BSD.) And it's not just the direct users of my software that I care about, it's also the overall ecosystem of freely available and modifiable software that I want to contribute to.

It also doesn't bother me when other people use OSS as an anti-competition mechanism. That's a different reason to do something that happens to resemble what I'm doing. It doesn't contradict or interfere with what I'm doing nor my reasons for doing it.

reply
>I think of it as a way for me to prevent other people from making money

That's a very common misconception I see among the developers. They get upset when someone sells their software, especially when the author distribute it for free.

Please read this: https://www.gnu.org/philosophy/selling.html

If the license doesn't allow to sell free software, the license is not free.

If you don't want others to sell your software, you need to use non-free license. There's absolutely no shame for that.

reply
> That's a very common misconception I see among the developers. They get upset when someone sells their software, especially when the author distribute it for free.

No, that isn't the argument here at all. The argument is that the existence of OSS alternatives (for which there is no real reason to pay more than a nominal distribution fee, aside from contracted support) makes it harder for proprietary software to retain commercial value.

reply
>for which there is no real reason to pay more than a nominal distribution fee, aside from contracted support

FOSS doesn't mean you have to distribute the software for free. If you want to earn money from FOSS, just don't publish it and sell it instead. It doesn't make it less open.

I sell open-source software of myself and others, for example, quite successfully.

Linked article states:

>So if you are redistributing copies of free software, you might as well charge a substantial fee and make some money. Distributing free software is an opportunity to raise funds for development. Don't waste it!

It has been this way all these years, that's why I call it a common misconception. The GNU article by the link above is from 2012 or earlier.

reply
If you thought this through until its final conclusion then you would notice that open source developers would simultaneously be paid more money than proprietary company developers and charge less money than proprietary companies.

People would gladly pay you more because it means they have to pay less.

The only necessary requirement is that the payment goes down with the number of payers and that there is no free rider problem.

reply
The marxist larping is cringe. In my experience, people that are like this likely have 0 commits to actual OSS.

OSS is a great passion project for a developer that wants to take it on, and when the community comes together, they can do incredible things. From a social perspective, I'd struggle to find anything that's more empowering to the average person than the ability to spin up a Linux server and get going in like 30 minutes.

But support is lacking. Proper documentation can be lacking. The sheer amount of work required to host, fix, update, and keep uptime up on real software at a real business is beyond a hobby, and enterprise support is mandatory, not optional. There are legitimate legal requirements that need to be met.

The fact of the matter is that the nature of the capitalist system that exists in the western nations is the same system that allows for OSS to exist at all. Tailscale was hard as hell to develop. Docker was hard to develop. I love the opensource alternatives to these services. I wouldn't use them at my company.

reply
[dead]
reply
More like developers want to buy expensive cars and a second home. Software pay is GOOD.
reply
Absolutely not the case everywhere.
reply
For typical work on FOSS projects?

Even if you limit it to FOSS projects extensively used by massive corporations i is far from rosy.

reply