I've tried to push Python for many projects at our shop. But it always get shot down by We don't want to write in 2.x series as its going to go away, and 3.x ecosystem isn't ready yet.
The more this continues, the more some technology is going to eat Python's lunch.
If Python wanted to break backwards compatibility they should have done so with some big major changes. That would have been justifiable. Right now no one sees a reason to break backwards compatibility to go to a no-so-ready ecosystem at the expense little gains. At the same time no wants to write 2.x either.
At least people planning to maintain their code base for years aren't going to write in a major version that's going to go away.
Comments
I've tried to push Python for many projects at our shop. But it always get shot down by We don't want to write in 2.x series as its going to go away, and 3.x ecosystem isn't ready yet.
The more this continues, the more some technology is going to eat Python's lunch.
If Python wanted to break backwards compatibility they should have done so with some big major changes. That would have been justifiable. Right now no one sees a reason to break backwards compatibility to go to a no-so-ready ecosystem at the expense little gains. At the same time no wants to write 2.x either.
At least people planning to maintain their code base for years aren't going to write in a major version that's going to go away.