Re:CVE-2015-8126: Multiple buffer overflows in libpng
by rdtsc on Saturday November 14, 2015 @07:11PM
(#10567877)
Technology moves so fast that everyone has short memory, patience and attention span.
So stuff like this happens [this is a tongue in cheek scenario, treat it as joke, not criticism of particular people or framework]:
Developer1: "Argh, I can't figure out dependencies for this library",
Then someone comes along and "fixes" it:
Developer2: "Look, just static compile it / include all deps in a subdir some place. See, fixed! I even made a language / framework thingie to do this for you. Yeah, those stupid old packagers and OS people made such a mess...".
Developer1: "Oh wow so easy, I'll be using this and tell others to use it too." /goes to twitter...
A few years later, everyone uses the new shiny dependency-bundling library/framework thingie. Then a security vulnerabily hits and everyone realizes why those old boring packagers and OS people set things up the way they did. 6 days later everyone forgets and jump on the next new shiny framework. Cycle repeats...
So stuff like this happens [this is a tongue in cheek scenario, treat it as joke, not criticism of particular people or framework]:
Developer1: "Argh, I can't figure out dependencies for this library",
Then someone comes along and "fixes" it:
Developer2: "Look, just static compile it / include all deps in a subdir some place. See, fixed! I even made a language / framework thingie to do this for you. Yeah, those stupid old packagers and OS people made such a mess...".
Developer1: "Oh wow so easy, I'll be using this and tell others to use it too." /goes to twitter...
A few years later, everyone uses the new shiny dependency-bundling library/framework thingie. Then a security vulnerabily hits and everyone realizes why those old boring packagers and OS people set things up the way they did. 6 days later everyone forgets and jump on the next new shiny framework. Cycle repeats...