9
Breaking of two NPM libraries show that everything isn't right in FOSS ecosystem
(freelancemag.blogspot.com)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Hmm, I don't really agree with that article. The thing is, publishing something as open-source is trivial.
But, despite the opposite being written into basically all open-source license ("is provided as-is"), we expect every published piece of software to come with updates ad infinitum.
And you can't really plan for it. You can release many pieces of open-source software that no one will ever use. And then one of them happens to become popular by chance and suddenly you've volunteered for the role of Benevolent Dictator For Life.
I guess, you could leave the software published and as-is, i.e. stop releasing new versions, but I'm honestly not sure that's truly better for the users. By breaking their builds, they'll know they have to migrate to something else. If you just leave it unmaintained, security problems will creep in and bugs will remain forever unfixed.