21–30 of 88 posts
I don't see why "replace PHP" is needed in the title other than linkbait. This is just a CGI dealy for Node. Even the article says "It can run along side PHP."
Because a large section of the php ecosystem is cgi and inline HTML. That was part of the original appeal and the reason it endures on budget hosts.
I thought PHP didn't run as CGI, shelling to a separate program with every request. It runs, in nearly all installations, as a plugin, saving the overhead of spawning a new program.
That's just one of the many reasons it did so well back it the day because it allowed a server to handle far more requests than CGI based stuff.
This doesn't seem to replace PHP whatsoever. I thought PHP didn't run as CGI, shelling to a separate program with every request. It runs, in nearly all installations, as a plugin, saving the overhead of spawning a new program. That's just one of the many reasons it did so well back it the day because it allowed a server to handle far more requests than CGI based stuff.
Earlier quoted context omitted.
Because a large section of the php ecosystem is cgi and inline HTML. That was part of the original appeal and the reason it endures on budget hosts.
What's considered a budget host in 2015 when I can get a digital ocean server to do with as I please for 60$ / year
See: GoDaddy hosting, BlueHost/DreamHost/Hostgator, etc.
This is wrong way. Keep Node.js where it has to be
Is there a real use-case for this? IIS has run server-side JS for years, and nobody's really using it.
I don't see why "replace PHP" is needed in the title other than linkbait. This is just a CGI dealy for Node. Even the article says "It can run along side PHP."