3 ms·
> If you're developing an alternative implementation, you probably have a different architecture from the canonical version, and things that are easy to do in
by Animats 3y ago
> If you're developing an alternative implementation, you probably have a different architecture from the canonical version, and things that are easy to do in the main implementation might be very difficult to do in yours.
Yes. This is the classic problem with making Python faster. CPython started as a naive interpreter, one that just plods along doing what the code says without optimization. In CPython, everything is a dictionary and there's little real concurrency. This allows any code to patch anything else on the fly. Nobody does that much, but people scream if you try to take that out. So implementations which really compile Python have to be able to handle some thread suddenly modifying something out from under another thread.
- pjmlp 3y agoClassical Smalltalk feature `a become: b`, now everything is changed across the whole image, or after a redo in a Lisp Machine like environment. Yet both ecosystems were able to come up with JIT implemenations that can handle the "reboot the world at any moment" use case.
- igouy 3y agoDo 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?
- pjmlp 3y agoAs if there aren't Smalltalk and Lisp implementations with support for parallelism, and have naturally to handle such cases.
- igouy 3y agoBy "support for parallelism" do you mean invoke multiple VMs and use sockets or shared memory?
- pjmlp 3y agoYou know what I mean, no need to play lawyer, leading the witness.
- igouy 3y agoNo. As-far-as I can see those comments are unhelpful to the point of being evasive.
- pjmlp 3y agohttps://franz.com/support/documentation/10.1/doc/smp.htm https://franz.com/support/documentation/10.1/doc/smp.htm https://www.lispworks.com/documentation/lw80/lw/lw-multiprocessing-ug.htm https://www.lispworks.com/documentation/lw80/lw/lw-multiproc... https://www.cincomsmalltalk.com/main/products/foundation/matrix/ https://www.cincomsmalltalk.com/main/products/foundation/mat...
- igouy 3y agoAnd 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".