4 ms·
Is there really need for every language to have its own web stack? Most do work with FastCGI, but treat it as second class citizen (or so it seems as an outside
by zokier 15y ago
Is there really need for every language to have its own web stack? Most do work with FastCGI, but treat it as second class citizen (or so it seems as an outside spectator). This is somewhat similar effect to that every language seems to have its own package manager.
- draegtun 15y agoHave a read of these to see some of the benefits with having this abstraction: * http://search.cpan.org/~miyagawa/PSGI-1.03/PSGI/FAQ.pod#Why_do_we_need_this%3F http://search.cpan.org/~miyagawa/PSGI-1.03/PSGI/FAQ.pod#Why_... * http://www.reddit.com/r/perl/comments/h46mr/plackpsgi_ecosystem/ http://www.reddit.com/r/perl/comments/h46mr/plackpsgi_ecosys... * http://www.reddit.com/r/perl/comments/h6qqr/the_psgi_is_the_limit/ http://www.reddit.com/r/perl/comments/h6qqr/the_psgi_is_the_...
- zokier 15y agoI can understand why some newer, better protocol than CGI or even FastCGI might be useful. But why there isn't a "FastCGI 2.0" which would have the advantages that these language-specific middleware boast, but which would be language-agnostic on the server side. At least from my point of view most languages are not that much different that they'd couldn't fit in a common interface.