News for hackers. Stuff that matters.
Re:PHP vs Node js... Let's be honest: Node.js couldn't kill ... by moomin on Friday May 05, 2017 @04:57PM (#14276791)
TBH, PHP is viable for pretty much exactly as long as Wordpress survives and uses it. If that changed, I wouldn't fancy PHPs chances.
Re:PHP vs Node js... Let's be honest: Node.js couldn't kill ... by paulgrimes1 on Friday May 05, 2017 @07:42PM (#14277656)
I disagree. I've been using PHP for about eleven years now, even since the bad old days of PHP3, and I have never used, and generally advise against using, wordpress. PHP will be around long after wordpress.

I do concede that if PHP went away, WP would somehow survive, like some kind of post-nuclear cockroach.

Re:PHP vs Node js... Let's be honest: Node.js couldn't kill ... by exclusiv on Saturday May 06, 2017 @01:52AM (#14278921)
I'm in the same boat. I cranked a lot of things out with CodeIgniter back in the day. Expression Engine is superior to WordPress but if you like either I'd suggest Craft CMS now and moving forward. For general apps, I use Laravel or Lumen. And React PHP for scraping. And don't forget The League [1]. Lots of great PHP stuff out there.

[1] https://thephpleague.com

Re:PHP vs Node js... Let's be honest: Node.js couldn't kill ... by Daishiman on Friday May 05, 2017 @06:18PM (#14277208)
The vast majority of web sites run PHP for better or worse and that code ain't going nowhere.

The performance characteristics of Node are completely irrelevant for most sites. The developments model's inherent complexity and the moving target, however, matters very much.

Re:PHP vs Node js... Let's be honest: Node.js couldn't kill ... by camus2 on Saturday May 06, 2017 @01:41AM (#14278881)
> The vast majority of web sites run PHP for better or worse and that code ain't going nowhere.

The vast majority of blogs that are build in Wordpress. Remove all the blogs and corporate websites and I bet that's not the case anymore.

Re:PHP vs Node js... Let's be honest: Node.js couldn't kill ... by Daishiman on Saturday May 06, 2017 @08:52AM (#14280016)
You're saying that as if blogs and corporate websites weren't a humongous proportion of the internet.

And no, there's some pretty big, modern sites like Mailchimp which run on PHP.

There's literally no reason to use Node if you already have an effective backend with PHP because Node doesn't really bring anything new on the table, but it does bring along its own class of issues.

Re:PHP vs Node js... Let's be honest: Node.js couldn't kill ... by camus2 on Saturday May 06, 2017 @09:18AM (#14280101)
> because Node doesn't really bring anything new on the table

You can't write a production grade web socket server in PHP. and no ReactPHP isn't my definition of production grade. If your app is real time you just can't use PHP for that.

So yes, Node brings something new to the table.

Re:PHP vs Node js... Let's be honest: Node.js couldn't kill ... by Daishiman on Saturday May 06, 2017 @02:21PM (#14281573)
Which is trivially compartmentalized through a Node proxy server that takes up at most 1000 lines of code. Nobody's throwing out their code for that.
Re:PHP vs Node js... Let's be honest: Node.js couldn't kill ... by camus2 on Saturday May 06, 2017 @03:39PM (#14281876)
> Which is trivially compartmentalized through a Node proxy server that takes up at most 1000 lines of code. Nobody's throwing out their code for that.

You just said, Node brought nothing new to the table, obviously you were wrong.