undefined | Better HN

story

0 pointsjnbiche6y ago0 comments

> Not all of us move fast and break things here, unlike the web dev world.

I had to roll my eyes at that one. Fine if your industry is accepting the high risk of using deprecated releases for new software, but don't try to act like upgrading from deprecated software is "moving fast and breaking things". This deprecation has been announced for 6 years. Python 3 was released over a decade ago.

This ain't a new JavaScript built tool -- this is a carefully planned end-of-life situation for a very old piece of technology.

0 comments

gpderetta6y ago

Another option is of course to use tools that take backward compatibility seriously.

jnbicheOP6y ago

Sure, do that. I'm not a Python fanboy, and there were some issues with how the transition was handled. Move to another language if you have the manpower. I think in in this case, since they claim to not even have the manpower to do some relatively straight-forward migrations from Python 2 -> 3 and/or they have some dependencies on Python2, I'm doubtful that's even an option.

I'm just pointing out that it's a risky move to adopt a soon-to-be-deprecated programming language for new projects, given the potential for security issues that won't be patched. It's the kind of ignorant arrogance that has always bugged me about many companies with non-technical management (please note: these words are not directed at user kgrave given that this appears an edict from above at his company, and he's unable to change it).

j / k navigate · click thread line to collapse

0 comments

gpderetta6y ago

Another option is of course to use tools that take backward compatibility seriously.

jnbicheOP6y ago

j / k navigate · click thread line to collapse