use Perl

I'm not a big fan of MI, and I think the main reason is it's too freaking magical. This "feature" is a perfect example of magic gone bad. It adds a _tiny_ bit of convenience (arguably less than tiny) while adding significant headaches for those who don't understand WTF is going on.

You were being an asshole, but I don't think what you said was sexist.

I don't care about professionalism, but I think it's reasonable to ask for respectfulness. You can disagree without being insulting.

Also, there were only about 80-some attendees, not 140.

http://www.selenic.com/smem/

Just a heads up that I will be giving a one-day Moose class here in Minneapolis on Wednesday, September 23, 2009. The cost is a very low $120. Future classes will cost more, so take advantage of this while you can.

For more details on the class, please see my blog. You can pay and register via the Perl Review website.

Just a heads up that I will be giving a one-day Moose class here in Minneapolis on Wednesday, September 23, 2009. The cost is a very low $120. Future classes will cost more, so take advantage of this while you can.

For more details on the class, please see my blog. You can pay and register via the Perl Review website.

If you _could_ care less, that means you _do_ care. I think you _couldn't_ care less ;)

You are not mistaken. Moose draws on Perl 6 (and/or Perl 6's influences) for much of its feature set.

I think the butterfly by itself is fine, and could be incorporated into a decent site design. However, the site as it stands is an absolutely horrible combination of over-saturated colors. I literally can't look at it because it hurts my eyes (not figuratively, it actually is painful).

My issue is more with you promoting this as a good Perl example.

SRI can do whatever he wants, and should feel free to experiment and have fun.

But his marketing, while good from a marketing perspective, is a turn-off to me because it ignores all the existing solutions.

And was it really impossible to work with existing authors to improve their modules? No, of course not, and it's obvious SRI had no interest in doing so.

The fact that it has no dependencies makes it even more compelling.

Really? You honestly think that a webapp framework should also ship with its own object system, its own cookie parser, its own HTTP server, its own HTTP header system, and to top it off, its own new templating system!

I look at Mojo and can only think that it represents the height of foolish arrogance, and I for one am repelled by it.

Catalyst is far from perfect, but at least the Catalyst developers can concentrate on building a web framework rather than reinventing all the underlying bits.

"There is a person ..."

Great, now every candidate can wonder if it's them. I suppose you could argue that's the point, since it makes each person reconsider their behavior. OTOH, people acting badly may not know they're acting badly, and probably need to be told directly how their behavior hurt someone else.

It looks like with that sort of auto-type inference for literals you could do something like Haskell's pattern matching. That's very exciting, since it's something about Haskell that makes for very expressive code.

That commit threw out a lot of useful information. When someone comments "I don't know what this fucking function is doing when I call it", the confusion is important.

If you think that having "naughty" words is not okay in your source, fine (thanks, nanny). But please don't remove useful information just to delete the f-word.

If the numerous small project approach is to succeed, it needs to work because the recipients are self-motivated. I completed my grant without anyone nagging me or setting deadlines, and that should be the rule.

If people don't do the work they promise, they shouldn't get the money. Hopefully the money + getting shit done is a sufficient carrot.