Hacker News Reader

Comment by xlm1717 | Hacker News Reader

Python was supposed to kill PHP. Ruby on Rails was supposed to kill PHP. Now Javascript is supposed to kill PHP? Not a chance, at least in the near future.

View on HN

And PHP was supposed to kill Perl.

At the end of the day, all of the languages being discussed here are all capable of achieving the same goals for 99% of the problems presented. Every language has its pros/cons and brings something new to the table that we usually see the others adopt.

As a server-side language, PHP has pretty much killed Perl, hasn't it?

server-side as in... shell scripts/daemons?

or server-side as in... cgi/fastcgi serving to a client?

because I would say 'yes' to cgi/fastcgi, but 'no' to shell scripts/daemons.

There are a handful of really cool newish Perl frameworks, but unfortunately I think Perl 5's stigma is so far out there it will never gain any real traction. It seems that Perl 6 has a lot of the same stigma attached to it. I almost wish they would name it something other than Perl so that a fresh perspective could be used, it seems like it's going to be quite nice!

I meant the cgi part.

Anecdotal: as a shared hoster engineer I would say yes. Ten years ago there were loads of Perl apps running on our shared Linux and Windows boxes, these days it's a novelty to bump into anything written in Perl.

PHP pretty much killed Perl if you ask me. Perl is nowhere near where it was in the 90's.

GraphQL on Drupal

https://www.youtube.com/watch?v=p3gMSnaZrp8&feature=youtu.be

We'll always have PHP like we still have MUMPS.

This article doesn't say that JS is supposed to kill PHP. The last paragraph actually states the complete opposite.

Yeah I need my job !

Now, that's the attitude. Learn one language and pray not to be killed.

Reply on news.ycombinator.com