Gabor Szabo wrote: > The other day I was at a client that uses Perl in part of their system and we > talked a bit about the language and how we try to promote it at various > events. > > Their "Perl person" then told me he would not use Perl now for a large > application because: > > 1) Threads do not work well - they are better in Python and in Java.
When in need to execute things in parallels, I use fork() or POE. > 2) Using signals and signal handlers regularly crashes perl. I don't remember seeing regular crash because of signals. I even wrote some badly designed daemons which relied on a heavy use of signals. They had bugs, but not because of the signals per se. > 3) He also mentioned that he thinks the OO system of Perl is a hack - > that the objects are hash refs and there is no privacy. I still have not been bitten yet by this. Probably because I don't have heavy OO needs. And if I did, I would now use Moose. > So I wonder what hurts *you* the most in Perl? In terms of Perl itself, apart from the reference syntax, the thing that really annoyed me recently was the lack of advanced debug tools, for example to find memory leaks. None of the tools I found or was pointed to worked in my case. -- Sébastien Aperghis-Tramoni Close the world, txEn eht nepO.
