All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

Great conversation here. Glad that people are willing to engage in it thoughtfully. (Many thanks to Alias for the conversation starter.)

@educated_foo [perl.org]: The reality is that people are using Ruby, and Rails, for more than just scripting up "shiny-looking web page with minimal effort." (I'll concede the point about DHH's hair.) They're using it for all kinds of crazy stuff, like writing desktop applications and large-scale messaging services like Twitter. (All things that Perl can do equally well.)

I think we could use some good blogs on marketing and visual vs. functional design, etc. A website dedicated to grinding this particular ax would welcome. Articles in a well read online publication would be excellent. Ignorance can be cured.

Some of what needs to be done, may appear as simple window dressing. But a consistent style guide and resources for building Perl websites that would like to use it would be great.

There are a lot of unorganized efforts out there. Things like making it easier to install libraries and applications as a user with limited rights. And many module maintainers are rewriting their OO code making Moose the defacto standard.

This is fairly typical for open source projects. But Perl could definitely use some cat herding public health policy person(s) to help us all stay on top of best practices.

As a part-time Perl programmer, my Perl is a mismatch of old and new practices. With all the Perl resource scattered about, I never know where to go to find a rational discourse on current best practices and recommended libraries.

Alias, thank you for all your efforts. Dare I say, that I've heard Perl needs a pumpking...