3 ms·
Having been involved in some systems that make heavy use of actors I 100% agree. We call actors "concurrent gotos" as they bring all the "advantages" of gotos w
by noelwelsh 9y ago
Having been involved in some systems that make heavy use of actors I 100% agree. We call actors "concurrent gotos" as they bring all the "advantages" of gotos with the added "benefit" of concurrency. It's a very primitive model of concurrency, only slightly better than mutexes. There are much better models in the research community but few of the ideas have yet made it into usable systems.
- uryga 9y agoCould you give some references to those better models? Sounds interesting!
- noelwelsh 9y agoVery briefly: Process calculus, such as the pi-calculus and join calculus. Prototype implementation in Scala here: https://github.com/Chymyst/chymyst-core https://github.com/Chymyst/chymyst-core Lasp and Bloom: http://christophermeiklejohn.com/lasp/2018/03/02/lasp-vs-bloom.html http://christophermeiklejohn.com/lasp/2018/03/02/lasp-vs-blo...