For decades, discussion of software reuse was far more common than actual software reuse. Today, the situation is reversed: developers reuse software written by others every day, in the form of software dependencies, and the situation goes mostly unexamined.
Dependency Cultures - Richard Feldman | SSW 2026
A plan for open source software maintainers
It seems to me that this is a case where problems are in fact solutions to other problems. To wit:
The $70B Open Source Software Paradox
It’s no news that over the last 10-15 years, particularly noticeable in the last 5 years, the enterprise software industry has gradually transformed from complex, expensive, closed-source (proprietary) software stacks to extensible/configurable,...
Open Sources: Voices from the Open Source Revolution
The typical computer user owns lots of software that he bought years ago and no longer uses today. He may have upgraded his computer or changed brands, and then the program wouldn't work any longer. The software might have become obsolete. The program may simply not do what he needs. He may have bought two or more computers, and doesn't want to pay for a second copy of the software. Whatever the reason, the software that he paid for years ago isn't up to the task today. Does that really need to happen?
dependency
A dependency refers to another piece of technology (software or hardware) a technology depends on for using. In software, "dependencies" may refer to the entire network of dependencies or just the software part of it.
Where Did Software Go Wrong? | Jesse Li
Software is broken, but it's not because of NPM, startups, AI, or venture capitalists. A deep dive into how we think about and produce code, and how our software systems reflect the manic state of the modern world.
reuse
Reuse means the use of a piece of technology for new purposes, often ones that were never envisioned by the original designers. Reusability refers to design that makes reuse possible.
software rot
Software rot is generally thought of as degradation of software due to a changing environment. For example, a program written a decade ago may no longer work with new versions of the libraries it depends on because some of them have changed without retaining backwards compatibility. This kind of thinking encourages a culture where software becomes obsolete unless it is constantly maintained.
Prosperous Software Movement | Open Source Observer
Bringing sustainable funding to public goods by revenue-sharing towards dependencies
How open-source software took over the world | TechCrunch
It was just five years ago that there was an ample dose of skepticism from investors about the viability of open source as a business model. Fast-forward to today and we’ve witnessed the growing excitement in the space.
Home Page - Software Heritage
preserves software source code for present and future generations
History of free and open-source software
The history of free and open-source software begins at the advent of computer software in the early half of the 20th century. In the 1950s and 1960s, computer operating software and compilers were delivered as a part of hardware purchases without separate fees. At the time, source code—the human-readable form of software—was generally distributed with the software, providing the ability to fix bugs or add new functions. Universities were early adopters of computing technology. Many of the modifications developed by universities were openly shared, in keeping with the academic principles of sharing knowledge, and organizations sprung up to facilitate sharing.
The Rise of Open Source Challengers
A look at how OSS takes over the application layer + the potential end of closed source software categories
