props to this choice, but on the other hand, I would expect this behaviour from paid libraries/frameworks. The Debian patch was really 💀 Open source projects should be free and choose what's best for the project itself, otherwise they could offer a paid plan to help performing upgrades.
Could you evaluate how many % of code is considered "legacy" and kept there, just because of the "don't break ABI" rule?
@madduci I really don't have any way to do such an evaluation without spending a lot of time. Which seems a rather pointless exercise to spend a lot of energy on.
several things that are deprecated and thus have code we *could* shave off if we would bump the SONAME still share code with the new implementation as well
Mathias
in reply to daniel:// stenberg:// • • •Marcos Dione
in reply to Mathias • • •daniel:// stenberg://
in reply to Marcos Dione • • •mountain
Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)daniel:// stenberg://
in reply to daniel:// stenberg:// • • •fun bonus-fact: that was just a month after my second child, my son, was born.
My SONAME 4 kid.
Peter Bindels
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Peter Bindels • • •Torsten Robitzki
in reply to daniel:// stenberg:// • • •Michele Adduci
in reply to daniel:// stenberg:// • • •props to this choice, but on the other hand, I would expect this behaviour from paid libraries/frameworks. The Debian patch was really 💀
Open source projects should be free and choose what's best for the project itself, otherwise they could offer a paid plan to help performing upgrades.
Could you evaluate how many % of code is considered "legacy" and kept there, just because of the "don't break ABI" rule?
daniel:// stenberg://
in reply to Michele Adduci • • •Michele Adduci
in reply to daniel:// stenberg:// • • •I thought there was some kind of commentary in code with some keywords like "superseded by" or similar ones, so you could count them.
daniel:// stenberg://
in reply to Michele Adduci • • •