So please come take a look and check out her hand made jewelry and natural craft supplies. Thanks!
While reviewing the Ironman feed I came across this post by chromatic that lead me to review these slides by Stevan Little. I think its worth a look and not an immediate dismissal, which I can understand since previous projects to modernize Perl have not exactly met minimum goals (no offense to any of these projects, but as a working programming who also has a life with other interesting things going on, I really only have time for frameworks that I can actually use on the job).
I think its worth consideration given where its coming from. Stevan Little has not only had tremendous impact on Perl (I've in the past mentioned that Moose is the project that kept me in the community) but also as someone running a consulting company and providing various programming services, not just Perl, he's in a great position to help bust up the bubble/echo chamber we often have going in our community.
Additionally I have a further challenge which I will pose to myself and to all of you. Stevan said Perl tends to be too much a bubble or echo chamber. I would further add that often the echos I hear compromise of a single person or tiny group. People blog, but seldom comment on other blogs. We as a community don't have the habit of getting into converations about design patterns, or programming theory. We are social enough together, but we don't really build and communicate our thought ecosystem. Knowledge of core aspects of Modern Perl such as object design, web application development, evented code and all that are not well dispersed in our community. As a result our applications tend to resemble state of the art from 10 years ago, and innovations tend to not be broadly understood. For fun I started a Catalyst application, just to show something off, and you know what, that application looks nearly identical to the very first Catalyst application I did many many years ago. Now, you can't say that the industry and theory hasn't changed, since it clearly has. What has happend is that our conversation and expectations have become anchored by whatever documention happend to be put together first, and seldom evolved from that initial posting.
As a someone that loves Perl I have to say it really sucks that I end up reading blogs on node.js to better understand nonblocking code and its possible uses, pro and con, or I end up reading blogs on Rails if I want to engage in a conversation about modern MVC. So I'll be trying this coming year to comment more other other's blogs and to reblog the ideas I hear. I hope some of you do the same.
There was a few later additions to the Catalyst Advent for 2012, which happened due to trouble I had with my Internet connection. If you didn't look lately you should glance at:
And in particular please check out Day 26 which is a great retrospective on choosing Catalyst from a technology platforms perspective.
There was a conversation over on the Catalyst mailing list regarding the depth of articles for Catalyst Advent over the years. One thought I suggested was we could do worse than to identify some of the better articles over the years, modernize them if necessary and do a bit of Peer review to make them even better, and then wrap them up into a ebook or similar.
Octavian, that superhero that did NINE advent articles, jumped right on it and suggested the following:
(2005) Catalyst Advent - Day 11 - Caching
(2007) Making your Catalyst App Cache-friendly
(2010) Painless Memcached Configuration With Catalyst & DBIx::Class
(2005) Catalyst Advent - Day 15 - Sessions
(2005) Catalyst Advent - Day 16 - Adding RSS feeds
If there are better ways to add an RSS feed, it should be modernized.
(2005) Catalyst Advent - Day 18 - Catalyst::View::TT
(2005) Catalyst Advent - Day 19 - Testing
(2006) Day 7 - Testing with an External Web Server
(2006) Day 17 - Testing Catalyst Controllers
Eventually create a single big article or a serie of articles regarding testing.
(2005) Catalyst Advent - Day 22 - Action Types
(2005) Catalyst Advent - Day 23 - Static::Simple
(2009) Delivering Static Media with Catalyst
(2006) Day 1 - Getting started with Catalyst and Subversion
Maybe it can be modernized to use distributed source control systems like git and mercurial.
(2006) Day 2 - Handel
(2007) A Future Look at Mango
(2006) Day 3 - The Layout of a Catalyst Application
(2006) Day 9 - Web Services with Catalyst::Action::REST
(2009) Writing REST web services with Catalyst::Controller::REST
(2006) Day 10 - The Chained Dispatch Type
(2006) Day 13 - Adding Custom Headers
(2006) Day 18 - I18N
(2010) Internationalising Catalyst, Part 1
(2010) Internationalising Catalyst, Part 2
(2006) Day 24 - The Catalyst Community
(2007) Application Design Techniques
(2007) Catalyst + Open Flash Chart: Fancy graphs with minimal fuss
(2008) Making sparklines with Chart::Clicker
(2012) DRAWING GRAPH CHARTS
(2007) Adding Authentication to your Catalyst App
(2007) Inline Authentication Without Redirection
(2008) Progressive Authentication with Catalyst (Using OpenID)
(2011) Login, Authorization and User Administration
(2007) local::lib and Catalyst
(2007) Day 13 - $c->uri_for fun and profit
(2007) Catalyst Configuration: A to Z
(2008) Day 10. Dealing with Config::General's inability to provide single item arrays.
(2009) Configuration layouts
(2007) Advanced Search in web DBIx::Class based applications (with tags, full text search and searching by location)
(2007) HTML::FormFu - Handles forms, so you don't have to
(2007) Using plain classes as Catalyst models
(2008) Catalyst and nginx
(2008) Making Catalyst Sites Shine with Varnish
(2008) Day 8. Some notes on ACCEPT_CONTEXT, with and without antlers.
(2008) Custom URL styles with CatalystX::CRUD
(2011) Easy CRUD for your Catalyst App
(2008) Day 16. Catalyst 5.80
(2008) WrapCGI: CGI.pm in your Catalyst app.
(2009) Running CGI Scripts Under Catalyst
(2009) Loadable Traits for Catalyst Components
(2009) How DBIx::Class::ResultSet::WithMetaData can help keep your controllers clean
(2009) Keeping Your Model Reusable
(2011) Get fat this Christmas
(2009) A Tour of DBIx::Class::Helpers
(2009) An HTTP API in 5 minutes
(2009) An AJAX CRUD Interface with Catalyst and jQuery
(2010) Getting Started with Catalyst and jQuery (and jQuery UI)
(2009) Plack - A Fantastic Layer To Make Your App Deployment Easier
(2010) Creating an Easy to Manage Search Engine with Catalyst and ElasticSearch
(2010) Adding Simple Excel Support
(2010) Input Verification with Data::Manager
(2010) Creating reusable actions with Moose::Role - an example
(2010) Moose::Role, Moose::Util and DBIx::Class based Models (multiaction revisited)
(2011) The ControllerRole ChainAction Massacre (Part 1)
(2011) The ControllerRole ChainAction Massacre (Part 2)
(2012) Action Roles for cleaner, less stashy Catalyst Actions
(2010) Access the Twitter API through Catalyst
(2010) Integrating Facebook into your Catalyst application
(2011) 2011 Reflections - 5.90 and beyond.
The modules discussed in that article can be helpful to be presented...
(2011) Checking for leaks in MyApp.
(2011) Keep your libraries organized
(2011) Deploy Catalyst Applications with Starman and Apache
(2011) A Git Tutorial
(2012) Catalyst in 9 steps
...and the other 8 articles of this serie.
(2012) Dynamic forms with HTML::FormFu
(2012) SCALING IMAGES ON DEMAND
(2012) HTML::FormHandler & jQuery Validator
(2012) Combining assets
What do the rest of you think? Comments, additions to the list, etc? My thinking is to organize them on github as the first step.