4 ms·

The ghost of Perl5 lives on...

• gpapilion 7y ago
  I was thinking this sounded nearly identical to perl 5s threading implementation.
• Ultimatt 7y ago
  Good thing Perl 6 was created and has a fantastic multi threading story. https://docs.perl6.org/language/concurrency https://docs.perl6.org/language/concurrency https://youtu.be/l2fSbOPeSQs https://youtu.be/l2fSbOPeSQs
• zaro 7y ago
  That's what I thought also when I saw the article.
• _wmd 7y ago
  Whoever is downvoting this, please realize this design stinks strongly of something Perl5 had a long time ago, that almost nothing could make use of due to a variety of limitations. The question in my mind is how the Python design addresses the problems that made the perl equivalent so unusable. It's only had ~20 years of context to do better, so I'm hopeful
• fanf2 7y ago
  Yes this is very reminiscent of the interpreter threads model from perl 5.8 (2002) https://perldoc.perl.org/threads.html https://perldoc.perl.org/threads.html
  • tyingq 7y ago
    The warning there is worth pulling up here: "The "interpreter-based threads" provided by Perl are not the fast, lightweight system for multitasking that one might expect or hope for. Threads are implemented in a way that make them easy to misuse. Few people know how to use them correctly or will be able to provide help. The use of interpreter-based threads in perl is officially discouraged." Perl5 also had a similar queue based scheme for sharing data across the interpreters: https://perldoc.perl.org/Thread/Queue.html https://perldoc.perl.org/Thread/Queue.html