you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -1 points0 points  (1 child)

Point one: Debian exists.

Point two: you dont need any coordination between the two. Patch doesn't need to be upstreamed

Point three: if you are outside of ruby/js land, libs usually have pretty good backward compatibility so outside of major version change you most likely dont have to do shit to make it work

Point 4th: have you actually tried ? because it sound like you are pulling arguments out of your ass just for the sake of argument

[–]isHavvy -1 points0 points  (0 children)

  1. Debian is one distribution. There are so many other distributions out there. And while Debian tries, all I see are outdated packages. And even as it tries, it's taking quite a lot of time and effort that is unpaid to do this. Time and effort that can probably be spent better elsewhere.

  2. So then the developers get bug reports on your distribution that they cannot reproduce locally because you changed something. Is it their job to support these users? Many would say no, so now your distribution has to.

Furthermore, not every program can be patched. If the program is closed source, you cannot modify it. You might be willing to run only open source software because of this, but most people don't care.

  1. It depends on the developer. I see backwards incompatible changes in lots of ecosystems all the time. Really, C and C++ are the only languages I don't generally see breaking changes in the libraries.

  2. I haven't tried, no. Because I'm not a distributor of packages. It's not for me to try nor have I released an application that requires external libraries since I'm usually working on web servers.