News for hackers. Stuff that matters.
Re:Python 3 in Science: the great migration has begun by Animats on Sunday May 10, 2015 @03:32AM (#9519200)
The successor to Python 2 may, in practice, be Go. That's the direction Google is going. Google used Python internally for non-speed-critical tasks, but the performance was too low for anything that had to scale. A few years ago Google hired von Rossum, and Google had a project, "Unladen Swallow" to produce a faster Python.

It failed.[1]

Von Rossum is no longer with Google. Google hired others to develop Go, which seems to be a good language for doing server-side web-related work. It's fast, memory-safe, scales well on multiprocessors, and has lower development costs than C++. That's what Google needed in their business.

Google maintains many of the key Go libraries. They're well-exercised production code. This is not the case for Python 3, as I spent a painful month discovering. I have some technical criticisms of Go, but when I write something in Go, it usually works as expected without surprises. You can use Go for important work with confidence. Python 3, six years on, isn't there yet.

[1] https://en.wikipedia.org/wiki/Unladen_Swallow

Re:Python 3 in Science: the great migration has begun by BuckRogers on Tuesday May 12, 2015 @01:17PM (#9533289)
Failing something like Pyston taking over for 2.x, that is my plan. Going from Py2 (what I currently use) to Py3 doesn't really do anything for me at all. There's the constant threat online from people about 'support' and guilt trips, but the support that matters (library support) isn't going away anytime, if ever, with a 80%+ userbase in 2015.

So I'm going to stick with Python2, and if I migrate to anything it'll be Go. Though it'll likely just be also using Go. I've already worked through a book on Go a couple years ago. I have my complaints about it, but I also have my complaints about Python.

Nothing is perfect, but Go IS really easy to get started with, which is worth a lot to an individual programmer or to a team. I'm not sure it's flexible enough as a drop-in replacement for Python, but if forced it's good enough to completely replace Python, if this Python2/3 debacle isn't resolved.

I'm seeing Python as 2 separate communities now. Of course the Python3 diehards see that as the worst-case outcome, since their community is always the short stick. But I think we're here now and it'll remain this way.

Re:Python 3 in Science: the great migration has begun by maxerickson on Sunday May 10, 2015 @08:49AM (#9519755)
Von Rossum worked on App Engine, he didn't work much on Unladen Swallow. You can see it here:

https://code.google.com/p/unladen-swallow/source/list

Google hired the Go guys years prior to Unladen Swallow even being an idea, and the first open source versions of Go were available around the time that the Unladen Swallow project plan was put out:

http://golang.org/doc/faq#history