6 ms·
Fifteen years ago, people would have found this interesting.
by rnadna 14y ago
Fifteen years ago, people would have found this interesting.
- almost 14y agoThere's no need for snark, it adds nothing to the conversation and makes you seem like a bit of a dick. There's a load of interesting stuff happening in Perl, I don't use the language myself but I'm interested in what they're up to.
- peteretep 14y ago15 years ago you could have replied to it on /. with "F1rst P0st" and been vaguely relevant.
- lloeki 14y agoDespite being a pythonista at heart and a rubyist at work, Perl is still my go-to language for when I notice bash scripts getting messy and growing out of scope and destined to enrich my personal long-term unix toolset. Yes, Perl is still very relevant today, for me and for countless others[0] [0]: https://github.com/languages https://github.com/languages
- mogrim 14y agoOut of interest, why do you go to Perl instead of Ruby?
- protomyth 14y agoFor myself, it is CPAN and documentation.
- lloeki 14y ago1. It's everywhere. By that I mean my code will work everywhere, without much thinking about it being installed, versions, or packages, or whatnot. 2. Ruby is too 'core' and needs too much additionals gizmos to be efficient 3. Ruby is concise and conventional, while implicitness and terseness are idiomatic of Perl 4. I'm no Perl monk but things in my head translate to code structure more easily in Perl for this use case (unix tools, text/binary/file content stream manipulation) 5. Perl strict mode 6. Occasionally, Perl suid support 7. Bonus: performance under Windows, or rather lack thereof for Ruby Mind you, Ruby is extremely apt and I enjoy working with it (especially - but not only - with Rails), but this is more a matter of using the right tool for each problem.