--- On Wed, 1/7/09, Paul Fenwick <p...@perltraining.com.au> wrote:
> From: Paul Fenwick <p...@perltraining.com.au>
> Subject: How can I best showcase Moose at a conference talk?
> To: moose@perl.org
> Date: Wednesday, January 7, 2009, 9:31 PM
> G'day Moosers,
>
> I'm giving at talk at http://linux.conf.au/ in two
> weeks time on cool things
> that people may have missed in Perl. I'm expecting an
> audience of somewhere
> between 100-300 people, most of whom I don't expect
> will have only minimal
> Perl experience.
>
> One of the many technologies I'll be talking about is
> Moose, and my main
> goal in showing it is to try and dispel the myth that Perl
> has to be ugly,
> and that Object Oriented Perl has to be a pain in the arse.
>
> With that in mind, is there anything in particular that I
> should be showing
> off but which I may have missed? Feel free to suggest the
> obvious here, but
> be aware that anything I show off needs to be accessible to
> "end users" of
> the language, and I won't be able to go into anything
> in too much depth.
>
> Caelum and gphat on #moose have already mentioned
> MooseX::Method::Signatures
> and MooseX::Declare, both of which provide a shinier
> interface, and hence
> suit my goals nicely.
>
> Cheerio,
>
> Paul
You might want to look at the "Unsweetened.pod" stuff, which really shows you
all the boilerplate and lifting that Moose is doing for you. That's provided a
great "Ah ha" moment for a few people I only had a few minutes with.
I'd also humbly plug MooseX::Types::Structured, which although is a Moose types
extension (not core Moose) gives you really neat abilities to describe your
type constraints and with recent updates to MooseX::Types even allows recursive
type constraints. I'd also say it's a great example indicating growth and
diversity within the Moose software 'ecosystem'. I believe that Moose promotes
an unprecedented level of knowledge sharing and accommodation among an
expanding group of like minded authors, promoting sensible standards without
unduly trampling the Perl individualist philosophy. "More than one way to do
it" promotes a healthy competition, but can sometimes lead to extremely
fragmented and unconnected development. Moose type constraints is a perfect
example of this. How many CPAN distributions are floating around that offer
some type of argument validation? In the absence of a community and a sensible
framework most gathered little mindshare and
even less patches and commits. So I think all the MooseX stuff as well as how
core Moose has integrated new developers is a sign of amazing success. I would
say that Moose is a great framework as well as a major win for the Perl
community.
John (jnapiorkowski)
