31 ms·

Rewrite in Rust!

• tetha 9y ago
  Seriously. Look at how google handles the Python2 to Python3 gap. They built a python2-go bridge and they are probably rewriting everything python2 in go. Make something expensive enough, and companies with resources will react.
  • paulmd 9y ago
    The truly hilarious thing about the Python 3 switchover is that they didn't take the opportunity to remove the GIL at the same time they were making all the other breaking changes. I guess rewriting all your code is one thing but rewriting it under the assumption of concurrency is just a bridge too far.
    • brianwawok 9y ago
      Or like this is post 7,345 where someone has to explain for many apps the GIL literally does nothing bad for you. Not all apps need concurrent threads in the same process.
    • scott_s 9y ago
      Removing the GIL has nothing to do with making breaking changes in the language. It's also an enormously more complicated task, one which hundreds (thousands?) of developers have spent time on over a decade (two?). I think you might be thinking that the impediment to removing the GIL is user code. It is not. The impediment is that CPython - the standard Python runtime - was designed around using the GIL, and it's extraordinarily hard to remove it and still meet the existing single-thread performance goals. There are also ancillary issues surrounding user code - particularly modules written in C, I believe - but the runtime itself is the biggest issue.