LWN: Comments on "The sustainability of open source for the long term" https://lwn.net/Articles/786304/ This is a special feed containing comments posted to the individual LWN article titled "The sustainability of open source for the long term". en-us Tue, 21 Oct 2025 07:03:13 +0000 Tue, 21 Oct 2025 07:03:13 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net The sustainability of open source for the long term https://lwn.net/Articles/787849/ https://lwn.net/Articles/787849/ karim <div class="FormattedComment"> Over the past ~25 years, I've seen the following work (really quick list, I'm missing quite a few things probably):<br> <p> - Provide services around an OSS package, use your work on the package as marketing. Several projects and companies work very well this way.<br> - Work for BNC (big name corp) that depends on mainstream OSS you contribute to. Works great for many kernel developers.<br> - Big corp commoditizing non-differentiating functionality by open-sourcing it. There's a ton of OSS coming from this, from very large companies. Most players now understand that this is a great way to keep the cost of non-differentiating software down and generating "positive" marketing from developers.<br> - Gaining geek cred by open sourcing toy project you worked on. Lots of that of this sort of abandware on github, but sometimes they contain some nuggets that are hard to come by.<br> <p> I've seen the following not work or work very unevenly (forget RedHat, it's the exception):<br> <p> - Open core. This looks good on paper, but doesn't work in real life, except for very niche products ... which end up not too far from the project+services model mentioned earlier.<br> - "Opt-out" dual-licensing models with commercial license available. This almost invariable ends up being bait-and-switch if it's led by a company. Affero-licensed software is almost always of this sort.<br> - Commercial offering with "toy"/crippled OSS version available. Slightly different from open core, more prevalent in the early days when some companies who didn't do OSS tried to get into OSS.<br> <p> In short, I don't see VC'able OSS as viable -- though I know some VCs say they "specialize" in this. But you can live "well" on working around OSS.<br> <p> </div> Wed, 08 May 2019 15:12:40 +0000 The sustainability of open source for the long term https://lwn.net/Articles/786729/ https://lwn.net/Articles/786729/ mathstuf <div class="FormattedComment"> The transcript reference has been fixed for those checking out the transcript now.<br> </div> Thu, 25 Apr 2019 14:11:45 +0000 The sustainability of open source for the long term https://lwn.net/Articles/786726/ https://lwn.net/Articles/786726/ mathstuf <div class="FormattedComment"> There was an episode of The Changelog recently which mentioned a VC firm focusing on just funding FOSS(-based) ventures. Roaming the comments, I found this[1] which mentions something called "Oasis Capital", but that looks to be something completely different at first glance. Further searching finds OSS Capital[2] which is likely what was meant.<br> <p> Now whether Tidelift is backed by them or not, I don't know. But there are FOSS-aware VC firms out there.<br> <p> [1]<a href="https://changelog.com/podcast/341#transcript-76">https://changelog.com/podcast/341#transcript-76</a><br> [2]<a href="https://oss.capital/">https://oss.capital/</a><br> </div> Thu, 25 Apr 2019 13:48:36 +0000 The sustainability of open source for the long term https://lwn.net/Articles/786669/ https://lwn.net/Articles/786669/ rgmoore <blockquote>When leftpad can become a separate project, project number inflates quickly.</blockquote> <p>I would guess there's a question about direct vs. indirect reuse. The number of people who directly include something like leftpad in their projects is probably much smaller than the number who use it indirectly by using a library that uses it. If you count "users" as only those people who use it directly, the numbers would get a bit more manageable. <p>There's also the question about how people would change their usage patterns if they were paying for the code they reused. The chances are people would be a lot more reluctant to reuse a tiny function like leftpad if it were costing them $1 every month. Instead, they'd rewrite little things like that, or somebody would make a bigger utility library that people could include as a big chunk instead of including dozens of functions separately. Programming languages with large standard libraries would have a big competitive advantage because they'd save their users real money compared to ones that require large numbers of external libraries to get anything done. Wed, 24 Apr 2019 21:42:17 +0000 The sustainability of open source for the long term https://lwn.net/Articles/786664/ https://lwn.net/Articles/786664/ nilsmeyer <div class="FormattedComment"> What is worrying me is that this is a VC funded venture, how are they going to produce the gains a VC requires while also serving their customers? Sustainability and the profit needs a VC fund needs to achieve aren't really well aligned. <br> </div> Wed, 24 Apr 2019 20:49:47 +0000 The sustainability of open source for the long term https://lwn.net/Articles/786660/ https://lwn.net/Articles/786660/ jake <div class="FormattedComment"> <font class="QuotedText">&gt; The bulk of the issues the article complains about are opened by other devs.</font><br> <p> I'm sorry you see it that way. The article was not meant to *complain* about the issues being filed, but to instead report what Luis said about how that increases the demands on the maintainers of these projects. He was not complaining about it either, just noting that GitHub has made it easier so people can more easily file issues, so they do. Apparently I worded my replay of what he was saying poorly.<br> <p> jake<br> </div> Wed, 24 Apr 2019 20:20:36 +0000 The sustainability of open source for the long term https://lwn.net/Articles/786657/ https://lwn.net/Articles/786657/ nim-nim <div class="FormattedComment"> The average user is not on github.<br> <p> The bulk of the issues the article complains about are opened by other devs.<br> </div> Wed, 24 Apr 2019 20:08:59 +0000 The sustainability of open source for the long term https://lwn.net/Articles/786651/ https://lwn.net/Articles/786651/ halla <div class="FormattedComment"> The article as is, is a bit weird, but your reply is weirder. And honestly, once you start getting a dozen bug reports a day, the value of a bug report is about that of an idea proffered by a fan to a novelist.<br> <p> And yes, I've been maintaining a software project since 2004, and I've had to cut down on user support in order to stay sane, and I've had to make a clear separation between the place where users report issues, and the place where my developers look for work, mostly.<br> </div> Wed, 24 Apr 2019 18:25:07 +0000 The sustainability of open source for the long term https://lwn.net/Articles/786636/ https://lwn.net/Articles/786636/ pizza <div class="FormattedComment"> <font class="QuotedText">&gt; Sad to see the average dev still does not understand what maintenance means.</font><br> <p> You may be correct, but the average developer still has a far better understanding than the average user. (The phrase "entitled prat" comes to mind...)<br> <p> <p> </div> Wed, 24 Apr 2019 16:27:21 +0000 The sustainability of open source for the long term https://lwn.net/Articles/786631/ https://lwn.net/Articles/786631/ nim-nim <div class="FormattedComment"> <font class="QuotedText">&gt; if these maintainers could, say, get $1 per month from each of their users</font><br> <p> What a completely unrealistic assessment. Don’t people have any idea of the scale of software reuse nowadays? Anyone on lwn is using thousands of different projects every month (sometimes tens of thousands). Probably quickly approaching the tens of thousands. When leftpad can become a separate project, project number inflates quickly.<br> <p> <font class="QuotedText">&gt; When you have 1000 users who needed to sign up with a Bugzilla instance somewhere to file a bug, the average response was to file no bugs</font><br> <p> And that was good, exactly, why?<br> <p> <font class="QuotedText">&gt; many developers would rather have help with bug triage than receive money for their work; they just want to get their time back, he said</font><br> <p> I'm quite sure a lot many issue reporters would want their time back too, since a lot of those are (auto) closed (sometimes quite rudely). Sad to see the average dev still does not understand what maintenance means.<br> <p> If you don't want to maintain your software just do not open an issue tracker. If you open an issue tracker don't complain people use it. Writing a report is work too. Just try to spend a day forcing yourself to report the problems you hit in the software you use, you'll see how far you will last.<br> <p> <p> </div> Wed, 24 Apr 2019 16:13:26 +0000 The sustainability of open source for the long term https://lwn.net/Articles/786591/ https://lwn.net/Articles/786591/ mjthayer <div class="FormattedComment"> The Tidelift web page says that it leaves projects to manage things as they see best, not putting any support requirements on them or similar. I would think that there ought to be some way for projects to provide extra benefit to Tidelift supporters to prevent a tragedy of the commons. Extra support would be an obvious place. I wonder if the Tidelift people have or are considering making that easy.<br> </div> Wed, 24 Apr 2019 12:46:49 +0000