Hacker News new | ask | show | jobs
by whiskeyjack 5538 days ago
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.

2 comments

Likewise my company is 100% PSGI for the last year+, we're a mix of a good number of Catalyst and Dancer apps. We've had absolutely 0 problems here.

PSGI stable, sane and the way you want to be doing things.

As both of you have a good experience of Plack/PSGI, could you sum up the benefit you got from using it?
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.

>Plack/PSGI has been embraced by almost everyone.

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?