5 ms·

We expect our choice of stack to be transparent for all developers. If it turns out it's the wrong choice, we'll either switch to Apache, or at least support bo

by shykes 16y ago

We expect our choice of stack to be transparent for all developers. If it turns out it's the wrong choice, we'll either switch to Apache, or at least support both. So far all alpha testers seemed very happy :)

bbbbbbbbb 16y ago
Well, I got the invitation and while playing around with nodejs, I was really looking forward for Perl support but this is absolutely not the environment I want to work on (wanted to use an in-house framework, not the ones listed and see if DotCloud could be of use for our clients). To tell the truth, this could be a good occasion to try to make the in-house app works in such environment but 1- don't see any real benefit 2- don't want to decipher the doc 3- no time (will have to work extra hours) you should definitely support both environment and not base your choice on the sole feedback of one person (you know... TMTOWTDI)
- jpetazzo 16y ago
  Hi, Well, actually, we didn't pickup Plack from its author. When people started asking about Perl, we just replied with another question: "which framework? how? what?", and we tried extract the most common denominator. The vast majority told us about Mojolicious, Dancer and Catalyst. There seemed to be a pattern :-) Regarding the server interface, a lot of people seems to agree over Plack. We were the ones asking "hey, what about FastCGI?" - since I personally never had met Plack before. We were shown the Plack::*::FCGI modules and thought "okay, that seems cool". Then we had a look at the server options. We had already used UWSGI for the Python stack, and UWSGI has a PSGI module. Some might say that it's a bit experimental, but the authors are awesome people, always willing to fix bugs as fast and efficiently as possible. Of course, the author of Plack helped us to get everything straight - but paradoxally, he was also the one pointing us to cpanm, perlbrew and basic stuff like Makefile.PL. Now, to get back to you: what does your app look like? We would like to help and see how we can get it to run on DotCloud!
  - bbbbbbbbb 16y ago
    Dancer and Mojolicious are pretty new and I will not use them in production yet (not to say that our framework is better, way from that but just that it's not open to things like that: http://blog.kraih.com/mojolicious-116-emergency-release-please-upgr http://blog.kraih.com/mojolicious-116-emergency-release-plea...). Catalyst is a dependency hell made true,not for us either. Mojolicious and Dancer will certainly be nice and will look into it but not at this stage of development. >Some might say that it's a bit experimental, Because it is. It's nice to play with it though. But not quite yet to use for our clients. > but the authors are awesome people, always willing to fix bugs as fast and efficiently as possible. Won't be able to say to my client: well, you know, we've tried this experimental stuff but we met these bugs we can't do anything about. "hey, what about FastCGI?" This was a very good question and I would have answered go for it... Apache+FastCGI+CGI::Fast. That's quite common nowadays and I think well understood, well documented. cpanm is not necessary, I've never used it and am happy with cpan. oh, right, cpanm is by the same author right? perlbrew&locale::lib are nice things to have though. > We would like to help and see how we can get it to run on DotCloud! Apache+FastCGI+CGI::Fast,that will do for me. Apache+mod_perl,that will do (even though i don't use it). Having at the cutting edge technologies is nice, don't get me wrong but it would help to have at least a more stable or at least bullet-proof environment too.
    - whiskeyjack 16y 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.
      - nmcfarl 16y ago
        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.

by shykes 16y ago

bbbbbbbbb 16y ago

Well, I got the invitation and while playing around with nodejs, I was really looking forward for Perl support but this is absolutely not the environment I want to work on (wanted to use an in-house framework, not the ones listed and see if DotCloud could be of use for our clients). To tell the truth, this could be a good occasion to try to make the in-house app works in such environment but 1- don't see any real benefit 2- don't want to decipher the doc 3- no time (will have to work extra hours) you should definitely support both environment and not base your choice on the sole feedback of one person (you know... TMTOWTDI)

jpetazzo 16y ago
Hi, Well, actually, we didn't pickup Plack from its author. When people started asking about Perl, we just replied with another question: "which framework? how? what?", and we tried extract the most common denominator. The vast majority told us about Mojolicious, Dancer and Catalyst. There seemed to be a pattern :-) Regarding the server interface, a lot of people seems to agree over Plack. We were the ones asking "hey, what about FastCGI?" - since I personally never had met Plack before. We were shown the Plack::*::FCGI modules and thought "okay, that seems cool". Then we had a look at the server options. We had already used UWSGI for the Python stack, and UWSGI has a PSGI module. Some might say that it's a bit experimental, but the authors are awesome people, always willing to fix bugs as fast and efficiently as possible. Of course, the author of Plack helped us to get everything straight - but paradoxally, he was also the one pointing us to cpanm, perlbrew and basic stuff like Makefile.PL. Now, to get back to you: what does your app look like? We would like to help and see how we can get it to run on DotCloud!
- bbbbbbbbb 16y ago
  Dancer and Mojolicious are pretty new and I will not use them in production yet (not to say that our framework is better, way from that but just that it's not open to things like that: http://blog.kraih.com/mojolicious-116-emergency-release-please-upgr http://blog.kraih.com/mojolicious-116-emergency-release-plea...). Catalyst is a dependency hell made true,not for us either. Mojolicious and Dancer will certainly be nice and will look into it but not at this stage of development. >Some might say that it's a bit experimental, Because it is. It's nice to play with it though. But not quite yet to use for our clients. > but the authors are awesome people, always willing to fix bugs as fast and efficiently as possible. Won't be able to say to my client: well, you know, we've tried this experimental stuff but we met these bugs we can't do anything about. "hey, what about FastCGI?" This was a very good question and I would have answered go for it... Apache+FastCGI+CGI::Fast. That's quite common nowadays and I think well understood, well documented. cpanm is not necessary, I've never used it and am happy with cpan. oh, right, cpanm is by the same author right? perlbrew&locale::lib are nice things to have though. > We would like to help and see how we can get it to run on DotCloud! Apache+FastCGI+CGI::Fast,that will do for me. Apache+mod_perl,that will do (even though i don't use it). Having at the cutting edge technologies is nice, don't get me wrong but it would help to have at least a more stable or at least bullet-proof environment too.
  - whiskeyjack 16y 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.
    - nmcfarl 16y ago
      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.