toast0 6 hours ago

I'm a big BEAM person, but python 3.0.0 was released december 2008. At that time, I believe OTP R12 was current, and it only gained SMP support in R11. [1] In 2008, I don't know that it would have been clear that the BEAM would be a good target. And I don't know how switching to BEAM then would have addressed what I think is the core issue python 3 was working on, unicode strings; BEAM didn't start taking on unicode until R13 and IMHO, is kind of on the slow end of unicode adoption (which isn't always bad... being late means adopting industry consensus with less of the intermediate false steps)

[1] https://erlang.org/euc/08/euc_smp.pdf

Reply View 0 replies
pansa2 13 hours ago

Python’s core developers don’t even seem to care about other Python implementations (only about CPython).

There’s no way they would move to, say, PyPy as the official implementation - let alone to a VM designed for a completely different language.

Reply View 2 replies
  • throwaway81523 12 hours ago

    At the time of the original Py3 release, PyPy was not ready for wide use. Otherwise maybe there could have been a chance of it replacing CPython. They were in too big a hurry to ship Py3 though. Tragedy.

    Reply View 0 replies
  • pjmlp 11 hours ago

    Which is a pity, Python ends up being the only major dynamic language, where for all pratical purposes there is no JIT support, because while there are alternative implementations with great JIT achievements, the comunity behaves as if all that effort was for nothing other than helping PhD students doing their thesis.

    Reply View 0 replies