Re:Where are we in the Python 3 transition?
by snowwrestler on Friday January 01, 2016 @07:36PM
(#10824339)
It seems like kind of a double standard to say "I don't like that they released breaking changes, so I'm going to switch language." Isn't switching language an even larger breaking change?
Re:Where are we in the Python 3 transition?
by BuckRogers on Saturday January 02, 2016 @02:50AM
(#10825477)
It is, but if you have to do a rewrite anyway?
The real gem in the rough with Python2 is PyPy4. You don't have to rewrite anything, while gaining CPU performance as a feature and dropping the GIL.
If you're not gaining that, I would probably switch to another language too. Elixir, Go, Swift, among others are definitely worth porting too.
That could be, of course for me the lens I'm looking through is very much a personal one. Backwards compatibility is a very important concept to me and I really dislike breaking changes, especially when there is no graceful intermediate phase with deprecation and warnings and ample time to move. It's what completely turned me off drupal and python more or less did the exact same thing. I'm sure that for newcomers to python the result is a much improved experience but from my point of view this was an un-necessary hardship.