41–50 of 50 posts
I took a six month break from Perl. I know it better than any other language. I recently started using it again for one offs. I love Perl. It is so much fun to be totally fluent in a language. Then I wrote a one page app in it. Oh my god, I can't believe anyone still uses Perl. Its strange. I love it. I hate it. Its great. Its a piece of shit. I am familiar with Modern Perl practices... I just can't understand why an…
I took a six month break from Perl. I know it better than any other language. I recently started using it again for one offs. I love Perl. It is so much fun to be totally fluent in a language. Then I wrote a one page app in it. Oh my god, I can't believe anyone still uses Perl. Its strange. I love it. I hate it. Its great. Its a piece of shit. I am familiar with Modern Perl practices... I just can't understand why an…
These folks seemed to have no problem creating a big system in Perl: http://www.lacunaexpanse.com/
For web developments, be sure to check out the Mojolicious framework (created by the founder of Catalyst). When used with PSGI and Moose, a lot of interesting stuffs can be built. http://mojolicious.org
Folk should also take a look at Catalyst http://www.catalystframework.org/ , Dancer http://perldancer.org/ and Jifty http://jifty.org/ - they're all nice to work with. Dancer being my current fave :-)
Earlier quoted context omitted.
You listed a lot of things you need to get to get Perl to work for you. In big orgs that would mean a lot of battling. For me it's just not worth the fight when e.g. Python just comes with half those things.
How is this different from Python? I install Python and most of the libraries I want are included,(batteries included). I install Perl and most of the libraries I want are included, (batteries also included). With Perl I've got CPAN available to install any libraries that I may be missing. Python may have some advantages over Perl, but "alot of things needed to get the language to work for you" isn't one of them. In…
Earlier quoted context omitted.
How is this different from Python? I install Python and most of the libraries I want are included,(batteries included). I install Perl and most of the libraries I want are included, (batteries also included). With Perl I've got CPAN available to install any libraries that I may be missing. Python may have some advantages over Perl, but "alot of things needed to get the language to work for you" isn't one of them. In…
You didn't read my comment. The point is that in a big org I don't have CPAN. Not without a big fight. And the perl language comes with do-it-yourself OO (they're not packaging Moose with the distro now are they?) and a bunch of other problems that you have to have CPAN to fix.
Perhaps it's just your company that's dysfunctional, not all big companies.
Earlier quoted context omitted.
You didn't read my comment. The point is that in a big org I don't have CPAN. Not without a big fight. And the perl language comes with do-it-yourself OO (they're not packaging Moose with the distro now are they?) and a bunch of other problems that you have to have CPAN to fix.
I work at a company with 300,000 employees, and I had no trouble getting CPAN. Perhaps it's just your company that's dysfunctional, not all big companies.
And I wouldn't call it dysfunctional to not make it easy for people to be downloading all kinds of software for production systems.
Earlier quoted context omitted.
I work at a company with 300,000 employees, and I had no trouble getting CPAN. Perhaps it's just your company that's dysfunctional, not all big companies.
This would be a problem at every big company I've worked for that didn't already have something. Obviously it isn't a problem everywhere but knowing what I do about big companies I would say it's more likely than not. And I wouldn't call it dysfunctional to not make it easy for people to be downloading all kinds of software for production systems.
If only we felt the same way about letting people write their own software for production systems...
Earlier quoted context omitted.
How is this different from Python? I install Python and most of the libraries I want are included,(batteries included). I install Perl and most of the libraries I want are included, (batteries also included). With Perl I've got CPAN available to install any libraries that I may be missing. Python may have some advantages over Perl, but "alot of things needed to get the language to work for you" isn't one of them. In…
You didn't read my comment. The point is that in a big org I don't have CPAN. Not without a big fight. And the perl language comes with do-it-yourself OO (they're not packaging Moose with the distro now are they?) and a bunch of other problems that you have to have CPAN to fix.
I find the default install of Perl to have just as many libraries built in as Python does. So even if you can't access CPAN then neither Perl or Python has a library advantage out of the box.
Earlier quoted context omitted.
You didn't read my comment. The point is that in a big org I don't have CPAN. Not without a big fight. And the perl language comes with do-it-yourself OO (they're not packaging Moose with the distro now are they?) and a bunch of other problems that you have to have CPAN to fix.
I thought I did read your comment. However even if you can't access CPAN this doesn't change anything. I find the default install of Perl to have just as many libraries built in as Python does. So even if you can't access CPAN then neither Perl or Python has a library advantage out of the box.
The best part with Perl is the CPAN. If you know what you do, for quite a few areas you are crazily productive. It makes good economic sense.
My point is -- the size of the default install is irrelevant, the win is when you install stuff from CPAN. It is arguably better if the default install is thin, because then people/organizations will have routines to install stuff from CPAN...
(Other good points with Perl is that the language is fun and that the social culture of nerds is wonderful. The main negative ones for Perl are the trolling ("PERL is dead") and the learning curve.)
I took a six month break from Perl. I know it better than any other language. I recently started using it again for one offs. I love Perl. It is so much fun to be totally fluent in a language. Then I wrote a one page app in it. Oh my god, I can't believe anyone still uses Perl. Its strange. I love it. I hate it. Its great. Its a piece of shit. I am familiar with Modern Perl practices... I just can't understand why an…
My experience is the opposite. I've used Perl for one-page web apps. I've used Perl for one-hundred-page web apps. I've used Perl for HTTP load testing. I've used Perl for high performance messaging. I've used Perl for writing desktop apps. Every time I do it, I finish and say, "this is great". The code is easy to read. The code is easy to extend. The code is easy to test. The code is easy to deploy. And I had fun ma…
Me too. And I hung out in the same IRC channels as you, and I used the same style and followed the same trends. And you know what? My informed opinion remains ;)
Once you write a web app in Ruby, writing one in Perl seems very silly. There is too much syntax. There are too many special characters. There is nobody to collaborate with outside of IRC. Library support in my area is quite poor.
I've done a lot of data/matrix math stuff in Python lately, but I'm actually switching back to Perl for that - I am just not productive in Python.
I've never had Perl 'fail me.' It can always do most anything I need to do. Its just a question of whether it is the best tool for the job, and whether it is the most enjoyable tool for the job.