4 ms·
We use it at my workplace pretty extensively. Where possible, new work is done in Go, and as time and effort permits work is underway to port things to Go, but
by nchelluri 6y ago
We use it at my workplace pretty extensively. Where possible, new work is done in Go, and as time and effort permits work is underway to port things to Go, but there is enough legacy stuff in Perl like our (front-end, customer-facing) web application that sometimes new features are written in Perl.
Modern Perl using Moose is pretty nice to develop in. I find it much easier to express things in Perl than in Go, but I am not an expert in either language despite having several years practice with the former and a couple of years with the latter.
http://modernperlbooks.com/books/modern_perl_2016/ http://modernperlbooks.com/books/modern_perl_2016/
I'd say the biggest issue with Perl is that modules on the CPAN are slowly going stale, and that my understanding is that there is a lot of Perl (C) and XS (C FFI) code that is not actively maintained or necessarily properly developed (including, I believe, parts of the Perl runtime itself). This can lead to segfaults with who knows what behavior.
Take this with a grain of salt: I've never been a good C programmer.
An aside: one of my coworkers is a founder of MetaCPAN, which is a great site.