>>147994
>Every HTTP request triggers the forking of a new process on the web server
look up fastcgi
>it has no MVC architecture
framework issue not a protocol issues. see php and php larevel
>CGI also contains a security vulnerability which must be coded around to avoid parameter injection.
u have to do that anyways in any lang where you want to save and use user data.

it being "slow" or not scalable is quite retarded. take any modern nu web app vs some ol cgi bin, it rapes the nu web app in speed over and over.

now the issue with it being live (or i assume reactive/restful, that is just mixing js with some json end point)cgi can do that. now if you mean websockets, yeah cgi cant really do that and its not really even http to begin with but you can use websocketd and its basically the same as cgi scripting as you read std in and send msg to std out