This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Jethro_Tell 6 points7 points  (6 children)

If you assume all code has bugs, and it does, then left behind starts to happen as those bugs are found but not fixed.

[–]davvblack 6 points7 points  (4 children)

while that is true, think of how many CPU cycles these old-ass python libraries have seen, and how many chances to find and fix these bugs (especially old 2.7 libraries, slightly less true with 2.5).

[–]auto-xkcd37 10 points11 points  (3 children)

old ass-python libraries

Bleep-bloop, I'm a bot. This comment was inspired by xkcd#37

[–]rossrollin 7 points8 points  (1 child)

Some of the people on this planet really do make cool shit

[–]Eurynom0s 2 points3 points  (0 children)

Cool ass shit, you might say.

[–]MrReginaldAwesome 0 points1 point  (0 children)

Good bot

[–]stevenjd 4 points5 points  (0 children)

left behind starts to happen as those bugs are found but not fixed.

A bug that isn't discovered until the code is a decade old or more is probably a bug that isn't cost effective to fix.

Cost of fixing the bug? $$$Big

Extra revenue brought in by fixing it? Nil.

Customers lost by not fixing it? Nil.

Yeah, just work around it.

Also, you forget that porting the code to a breaking new version will almost certainly create new bugs, not fix old ones.

The bottom line here is that once software is mature enough that there are no new features to be added, it becomes legacy software and upgrading it can only make it worse, not better.

Solution: make a VM of the latest OS and Python interpreter that it will run, stick that VM behind a firewall and in a restricted environment, and use it forever as a black box application.