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.
If your app (or your framework) runs on Plack/PSGI you have a wide choice of server implementations. It will work under mod_perl, FastCGI and numerous other server environments.
Indeed if you write an app to run on DotCloud; you can also run the same app on your laptop, Phenona, any other server -- etc etc.
As someone else said (more politely), you'd have to be nuts to do an HTTP app now and not take advantage of it.
In your company or in general?
Because if it's in general, I would be more than happy to see where you get your stats.
> You do Miyagawa a disservice implying he's pumping his own code.
Well, I do think that a not even 2yo spec,a set of modules that are 6~18 months old pushed on a cloud service like that with no back up plan for more "traditional" systems is a way to push its own system. we can agree to disagree on that.
which percentage of providers offer plack with nginx nowadays compared to Apache with FactCGI?
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 really don't communicate with the Perl community at all. I write code, I send bug reports or bug fixes if things are broken.
I really don't see how interacting with the Perl community would be relevant to an employer from an engineering point of view.
At that point it's not 'savvy' people who know that, but silly people who have too much time to complain or notice small things like that. Possibly managers or scripters, not engineers who go only by code, architecture, etc.