6 ms·
Is anybody surprised by this? Everybody knew the transition was going to take a long time, and that it would be a gradual process. It may be that it's actuall
by mindcrime 11y ago
Is anybody surprised by this? Everybody knew the transition was going to take a long time, and that it would be a gradual process. It may be that it's actually been even slower and more gradual than people expected, but by and large everything seems to be proceeding nicely.
- godzillabrennus 11y agoI don't think anyone expected a lengthy transition at the onset of the version 3 release. It's taken a long time and the 2.X releases that have come along since have helped make the transition easier by showing developers some of the benefits from version 3 releases.
- EliAndrewC 11y agoI was on the "Python 3000" mailing list while it was being planned, and the prevailing attitude seemed to be "it'll probably take 5 years before the community moves to Python 3". (That's paraphrased and not a direct quote, though I saw people say that sort of thing almost word for word a few times.) This was optimistic, but at least we see that the community is indeed gradually moving to Python 3, even if it's taking a few more years.
- brettcannon 11y agoTechnically the goal was a majority of new projects started using Python 3 in 5 years. Regardless, everyone knew it would take several years to reach a point like this.
- mangeletti 11y agoExactly, and I, for one, was using Python 3 for a new app, in production, in 2013, precisely 5 years after the release.
- philipov 11y agoI switched from Perl to Python at version 3.4, and while it might be popular for people already invested in Python 2 to downplay the syntactic improvements, they were a big deal in convincing me to switch to Python as my go-to infrastructure language.
- ceronman 11y agoThis is true, but currently, most of developers of Python acknowledge some mistakes in the Python 3 transition. Specifically the fact that such an abrupt compatibility break was underestimated. And that's why Python 4 won't break compatibility with Python 3. In any case, I'm very happy to see the Python 3 transition moving forward. And let's hope this does not happen again.
- mangeletti 11y agoIMHO, this is incorrect. Python's back-porting of 3.x features caused Python 3 adoption to take even longer (no pain, no gain). But, I think this was a necessary evil, because if PSF had forced everyone with a "upgrade or perish" attitude, I think many would have abandoned Python.
- jamwt 11y agoPretty sure there would be a fork. Many large tech companies (Google, Dropbox for two) are deeply invested in Python 2, and some of us already have some modifications to CPython. Python 2 is Too Big to Fail.
- deleted 11y ago[deleted]
- TorKlingberg 11y agoI disagree. The main thing holding back Python 3 use has been library support. Library developers do no want to maintain two separate codebases, so it is very important that a certain subset of the language works under both 2 and 3. The backported features in Python 2 and some backwards compatibility added to Python 3 in recent years have really helped with that.
- andrewstuart2 11y agoAnd actually, that may be a great sign of a healthy, mature community. Python has reached and held a level of maturity at which change happens slowly and methodically. In fact, Google Trends [1] seems to indicate that, too. After what was probably an initial stomach-drop of broken compatibility, python is picking up a lot of new developers again. https://www.google.com/trends/explore#cat=0-5-31&q=python&cmpt=q&tz=Etc%2FGMT%2B7 https://www.google.com/trends/explore#cat=0-5-31&q=python&cm...
- mindcrime 11y agoI consider the Tiobe Index to be fairly suspect, but FWIW, their most recent ranking has Python moving up a few spots: http://www.tiobe.com/tiobe_index http://www.tiobe.com/tiobe_index It doesn't, AFAIK, distinguish between Python 2.x and Python 3.x though. But the trend seems generally favourable for Python in general.
- andrewstuart2 11y agoHaha maybe it's just the HN effect but I was very surprised to see Java at ~20%, having increased ~5% over the last year (I guess Android is Java, though). That, and the facts that Rust is ahead of Go, and that the two of them sit at only ~0.4% usage combined.
- BigJono 11y agoCOBOL and Fortran usage more than triples Rust and Go usage. Just to put things in perspective a bit further.
- mastazi 11y agoI can actually see that as being real. There is a lot of legacy code out there (especially in larger corporations) and, while these languages are rarely featured in the news, many people are required to use them at work.