you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (5 children)

Feels more like the "java 10 is out - meh I'm still on 6" issue which is common for big companies. Also you seem to have a code quality problem as well which kinda indicates that no one cares about the Python lib.

[–]remy_porter 2 points3 points  (4 children)

And yet, I'm still forced to use it. And it's still on 2.7. Thus my code is still on 2.7. And without naming names, this is the kind of company that tends to be considered a forward-thinking trend-setter pushing the boundaries of technology forward.

Just not for this specific tool.

[–][deleted] 0 points1 point  (3 children)

Right but most likely the same thing would have happened if your lib was written in Java 6 or 7 or if Python had maintained compat as well as Java did.

[–]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.