Re:The Linux 2.5, Ruby 1.9 and Python 3 release management a...
by derefr on Monday December 26, 2016 @10:21PM
(#13261078)
I feel like the only responsible thing to do in such cases—if you truly believe that the thing you're abandoning is just a plain-old failure of engineering, and it's effectively self-flagellation to be subjected to maintaining it—is to poison the well/salt the earth when you leave, so that people are at least forced to switch to something else, if not your replacement project.
Badly-engineered buildings get condemned, and we make it illegal to use them, even if it might benefit someone to use the building in exchange for the (likely not-very-well-considered) risk of the roof falling on them.
What sort of political/social infrastructure would it take to allow someone to condemn a codebase?
Re:The Linux 2.5, Ruby 1.9 and Python 3 release management a...
by kibwen on Monday December 26, 2016 @10:42PM
(#13261151)
Google has begun building "time bombs" into Chrome that will start inconveniencing users once the binaries reach a certain age without being updated (I believe this is specifically related to certificate validation, but I'm not going to look up details because I don't want to be put on a watchlist for googling "chrome time bomb" :P ).
Re:The Linux 2.5, Ruby 1.9 and Python 3 release management a...
by scrollaway on Tuesday December 27, 2016 @01:13AM
(#13261597)
One example is the original V8 dev team that went off to create Dart (AIUI). Nobody followed them and V8 got replacement developers. (But perhaps that was a particularly egregious case.)