I resepectfully disagree. My company has two PSGI Dancer apps running mission critical elements. They're "new" but they're absolutely production ready. Plack/PSGI has been embraced by almost everyone.
I'm REALLY looking forward to playing with DotCloud.
Plack/PSGI is not "cutting edge". It's the way to do it now, not tomorrow. You do Miyagawa a disservice implying he's pumping his own code.
I switched to DDG about 3 months ago. If nothing else, the bang syntax is a huge win for me. Among my favs are !cpan !jquery !js !perldoc !php. Makes looking stuff up nice and quick.
This kind of behaviour is an embarassment to the community. It's poison.
Move along. If you claim there's stealing of code, prove it and show it. Otherwise, save this crap. You like Mojolicious. Fine. Go do that. The Dancer crew will continue on it's way. It affects you not at all.
I had investigated Mojolicious but this kind of attitude from you and from it's creator have long kept me out of that community. Yes, the channel can have people who are helpful, but bile begets bile and if you're an example of the Mojolicious community, I want no part of it.
I'll start this with "I'm a Perl programmer" but I'm not looking for a flame war. I am interested in hearing an expansion of your statements. I am going to admit I don't understand this one.
What do you mean by "Big Bang"? That Perl 6 is being developed on top of Parrot? That Perl 6 is a reinvention instead of re-iteration?
What "enormous resources" are you referring to? The Perl 6 team isn't huge and it's all volunteer with very little financial backing (only some relatively small grants from the Perl Foundation).
Which components are you referring to? Where are the "limited ability to test the compatibility of the components"? Which components? There are a lot of tests though... a truly massive test set. I'm assuming you're not referring to these.
From my understanding the "utility" is a pretty big part of what they're testing. There are folk writing Perl 6 (November wiki http://www.perlfoundation.org/perl6/index.cgi?november). The implementors are going back and forth with Larry about things. A lot of the ideas aren't new, just new in Perl.
I'm just trying to understand where you're coming from. :)
I would have liked to have seen "a lot less bad that it looks" replaces with "one would have been too many" and "we will work very hard to regain your trust". It's okay... but the public is their target audience! Simple phrases, big impact.
I'm kinda floored by the comments on the story on NPR. Even if you don't like'em, they're managing to pull off something not everyone can. I've enjoyed Pomplamoose for a while now. Glad to see they're doing well.
Then again, I guess it's just as shocking that I'm still surprised by the vitriolic tone of commenters on the internet.
This is a difficult dynamic to manage and depends really heavily on the designer and programmer involved, how good they actually are and how much they credit the others expertise.
I've worked on projects at one job with a designer that was top notch. He knew and understood the medium despite having started as a print designer. As he did with print, where he learned about the pre-press process, he made sure he learned about the web, usability and understood HTML and CSS. What a joy it was to work with him. His designs were beautiful and understood usability without sacrificing appearance. He's gone on to do independant work and now makes double what I do. Good on him.
Then there's the other side. I've worked with another designer who thinks design exists in a silo, refuses to learn anything about the medium and has very firm (and misguided) ideas about usability. They see no point in involving a programmer in the design phase because the programmer is just supposed to make things work and doesn't understand design. They have learned nothing about the web and feel learning HTML or CSS dilutes their focus; any designer that does know these things is looked down upon because they're spreading the attention to far and will make a poor designer.
Programmers can make it hard on a designer, even good ones, and we shouldn't. This is the most valuable working relationship you can form in my opinion.
If you find one of the former, hold on to them like they are the only life preserver in the ocean. If one of the latter, run like hell. There are, of course, many skill/knowledge levels in between but it really makes me appreciate it when I have a good one to work with.
I hate PHP with a passion but I think it's worth knowing about and I think the claim that "knowing C" makes it easy to interpret a PHP program is not a good assessment. Further, just knowning C doesn't mean you'll know the semantics of webdev... which is what PHP is all about. You get domain knowledge along with the language.
I'm also convinced that in almost every case that Ruby and Python are just fine in place of Perl... except for text processing.
Perl's regexp engine is top notch and is an extremely key part of the language in ways it just isn't in Python or Ruby, especially after the release of Perl 5.10. I don't see another language that can touch Perl there yet (feel free to correct me because I'd be interested to learn).