3 ms·
..No, not wanting to indefinitely maintain arbitrarily-old versions of a free and open-source security library is not "planned obsolesence".
by SEMW 3y ago
..No, not wanting to indefinitely maintain arbitrarily-old versions of a free and open-source security library is not "planned obsolesence".
- sylware 3y agoThe devil hides in the details.
- bee_rider 3y agoCould you elaborate on the details? It seems like a pretty silly thing, to engage in duplicitous business practices to sell more… free code.
- sylware 3y agoUsually, it is in non-pertinent ABI/API breakage. And companies which are making a business at upgrading components like openssl are the ones which would be targetted for a planned obsolescence crack down. Usually, it is c++ ABI issues (those are usually a massive pain), or glibc versioning manic usage, since there are rarely API/ABI breakages in many crypto libs.