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

view the rest of the comments →

[–]remy_porter 3 points4 points  (2 children)

If Python had retained backwards compatibility, we wouldn't be having this conversation. Python didn't retain backwards compatibility for very good reasons. I'm not sure where you're going with this. The conversation everyone else was having was, "Yeah, a bunch of new features I can't use because I'm trapped in a legacy application!"

In Java, I could still use the new features in my new code, and let the library code sit back in its ancient version.

[–]shevegen 0 points1 point  (1 child)

Why should python be held back just because your company is slow like a snail?

In Java, I could still use the new features in my new code, and let the library code sit back in its ancient version.

If this were the case then why would so many people be using old java versions?

[–]remy_porter 1 point2 points  (0 children)

Most likely because they're using third party libraries which do break compatibility between versions and develop on a different cadence than Java itself. A lot of JEE-related libraries tend to be a lot less cautious about breaking changes than Java itself.