3 ms·
> The "interpreter-based threads" provided by Perl are not the > fast, lightweight system for multitasking that one might expect > or hope for. Threads
by nandhp 12y ago
> 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.
That's too bad; I know that threads were very unstable and buggy, but I wish they had been improved them instead of considering them "to have been mistakes".
Also on the unfortunate side, CGI.pm has been deprecated and will need to be installed from CPAN.
On a happier note, IO::Socket::IP has been added; which finally gives Perl built-in IPV4/IPv6 parity (i.e. one module that can do the jobs of both IO::Socket::INET and IO::Socket::INET6).
- Mithaldu 12y ago> That's too bad; I know that threads were very unstable and buggy, but I wish they had been improved them instead of considering them "to have been mistakes". No snark: Patches welcome. There have been people who tried to implement better threads for Perl ( https://metacpan.org/release/threads-tbb https://metacpan.org/release/threads-tbb , https://metacpan.org/release/threads-lite https://metacpan.org/release/threads-lite ). However the task is such a monumentally difficult one, that unless you have considerable ressources available (Java, Go), you're unlikely to get a very good implementation of them (Python, Perl). Perl being entirely volunteer-developed means that there currently simply is nobody with both the knowledge, and the available time, to do this. If you think you can do it, or know someone who can, please by all means give it a try.