To add my five cents, the thing that hurts me the most is that Perl is
not an accepted language when it comes to the differnet new platforms.
Our work has adopted Drupal as a CMS and it's written in PHP. It would
be awesome if it was written in Perl, but as someone else posted in this
thread, we can pick up languages pretty easily (better than foreign
languages, no? ;)) and be productive in a few weeks.
I'm also attracted to the new Android and iPad platforms, but there's no
Perl there, either.
There's no Perl when it comes to creating client-side web applications
(using JavaScript).
IMHO, Perl is getting relegated to server-side/backend applications and
when more power is getting brought to the front, it's losing
mindshare/focus.
- Jason
http://use.perl.org/~Purdy/journal/31280
On 11/24/2010 07:01 AM, 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.
2) Using signals and signal handlers regularly crashes perl.
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.
So I wonder what hurts *you* the most in Perl?
Gabor
--
Gabor Szabo http://szabgab.com/
Perl Ecosystem Group http://perl-ecosystem.org/
