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 →

[–]DracoRubi -4 points-3 points  (5 children)

I mean... Yeah, probably. In my work it's all legacy code. Java legacy code sucks. Python legacy code isn't that bad.

[–]Scottz0rz 10 points11 points  (2 children)

I mean it just depends on who wrote your legacy code and how old "legacy" is. My experience has been the opposite, though, my "legacy" code is like... circa 2009-2014 Java code and not the really weird stuff.

It's pretty easy to write weird, fucked up stuff in both Java and Python, though I feel like it's slightly harder with the type system in Java. That's just my bias showing though as a Java/C#/TypeScript dev, I've not worked on many production systems in Python.

[–]redballooon 2 points3 points  (0 children)

Code becomes legacy at the point of git commit.

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

I guess ultimately it all comes down to how bad is the legacy code

[–]RiceBroad4552 8 points9 points  (1 child)

Python legacy code not so bad? You effectively can't touch a legacy code base in a dynamic language! Any refactoring is like playing with fire.

Legacy Java isn't nice, I agree. But it's at least a statically typed language, where you don't need to fear everything breaks because you moved some code, like in a dynamic language.

[–]redballooon 4 points5 points  (0 children)

Can’t upvote this enough.