Do you agree with them that "implementations which really compile Python have to be able to handle some thread suddenly modifying something out from under another thread"?
Would you say that's also true of Smalltalk implementations?
And when we look at that (proprietary Cincom Smalltalk) approach we find "simple mechanisms for spawning multiple running copies of the image and using those to perform various tasks in parallel" and "Objects are marshaled between the master and drone as copies, not as references."
That's not an example of comparable complexity to "… Python ha[s] to be able to handle some thread suddenly modifying something out from under another thread".
Would you say that's also true of Smalltalk implementations?