3 ms·
Why? It's either useful or it's not, and if it is and it's open source you can take it and use it or enhance it as you like. If your use of open-source code is
by SoftTalker 3y ago
Why? It's either useful or it's not, and if it is and it's open source you can take it and use it or enhance it as you like.
If your use of open-source code is predicated on the expectation that someone else will always be there to take care of it, then you're just a freeloader.
- StressedDev 3y agoIt really depends what ecosystem you are in. For example, the nodejs/npm ecosystem is on a never-ending cycle of package upgrades. If a maintainer is not maintaining a package, it will eventually have to be replaced for one of the following reasons: 1) One of the package's dependencies has a breaking change which breaks the package 2) One of the package's dependencies has a security bug. The dependent package cannot be upgraded to a fixed version because the dependent package's fixed version has a breaking change which breaks the original package. Basically, ecosystems which do not have strong backwards compatibility tend to require packages/libraries/creates/assemblies/DLLs to be maintained forever.
- Falkon1313 3y agoThat seems like a really good reason not to use that ecosystem. It's not the fault or the problem of the person who created the open-source project. If you choose to use open source code in a system like that, then that's what you've chosen.
- poulpy123 3y ago> Why? It's either useful or it's not the maintenance is not a small part of the usability of a software > it's open source you can take it and use it or enhance it as you like. No, I need to have the ability and the time to do so > then you're just a freeloader. I don't remember the part in the free software licence that doesn't allow me to chose to use or not use a specific software or a clause that force me to take over it's development in case the original dev abandon it