Comment by Mario Giambanco on "Is PHP + MySQL based stack still relevant in 2016?"

Absolutely!

The only people NodeJS / React / AngularJS / the Javascript Framework Wars mean anything to are startups that want to be fancy; programmers that want to be fancy or people that want to learn those frameworks.

You cannot trump the power of SQL - be it MySQL or Postgres or Oracle or SQL Server or etc...

Anyone freelancing and using Wordpress - yes, still incredible relevant.

Any web development shop - the kind you call to build you a website for your restaurant or small business - yes, still relevant.

Corporate work? If they are not using Java (not javascript) they are using PHP (or rails).

It's still wildly compatible with most if not all 3rd party services - Mailgun, Cloudinary, Stripe and others.

It can make cron jobs super easy - php myscript.php from the command line and done and done.

Your customers - don't care if the website uses React or AJS or whatever. They care that it works / fit their budget and can be maintained / upgraded easily. And as much as everyone and their mother might be trying to learn JS frameworks - there are many many more programmers that can jump right into a PHP program and pickup where the old programmers left of.

Frameworks come and go - PHP / Rails / Python are established languages that are here to stay for a long time, IMO.

What are you talking about? How did you manage to drag Node/React/Angular/JS into yet another discussion that isn't about any of those things? o_O

I feel like I'm picking on you now, but this is another reply that is full of misnomer and misinformation. First, the front end frameworks you mention have nothing to do with PHP. Second, what does "wildly compatible with most if not all 3rd party services" mean exactly? Thirdly I'd love to know where you think PHP gets its cron superpowers from? Fourthly, Rails isn't a language - it's a framework. Are you drunk?

Right, I took a walk away from my screen and I'm back with a slightly more constructive comment. I'll leave my existing comments for posterity (I believe in being responsible for what I say). The general gist of your response is OK - PHP is indeed entirely relevant, and won't be going anywhere for a while. However you're completely mudding your answer with jargon that simply doesn't need to be there, and information that is actually incorrect. I can only assume that either you don't know what you're talking about (which I do not believe is the case), or that for some reason you feel like you need to "buff up" your answers with terminology. I really don't want to criticise, especially publicly, but there's little provision for doing so otherwise. Hashnode is awesome and needs people like us to produce content for it to succeed, and I have nothing to do with its policing, so I'm really just asking you user to user, community member to community member, to be a little more diligent in your responses, and to perhaps consider that you might be doing something wrong if a few people (that I've seen) have said the same thing. Personally, I'm totally open to being corrected if I'm wrong, and I don't consider for a moment that I am absolutely 100% irrefutably correct. I'd actually be disappointed if my inaccuracies were left unchallenged. Criticism doesn't have to be abrasive.

The criticism is welcomed - even if sometimes, it does feel like your picking on me (lately) :). I definitely tend to go on rants and I definitely tend to mud up my answers - But - Bill's "tag line" is that he's into Javascript - one could only assume, he's asking this question in comparison to what he knows best, which is why I bring in JS and it's frameworks. (Also - because it seams, every other question here is regarding JS). I'm not against JS - I'm quite a fan of AngularJS and I really, have nothing against it. I do have a problem with vague questions (this isn't one of them) which has caused my rants and our disagreements in the past. As you said, this isn't the forum for this discussion and Hashnode doesn't have a private chat to do that. And the use of Rails - which I know - is a framework - was a mistake on my part. I was asked to participate in this question and answered quickly while distracted with other stuff on my plate. The proper language is Ruby obviously and was a mistake on my part. But as you said, to change that now, would confuse future readers. 'till next time, friend.

@mgiambanco I am so glad you responded. I'm definitely not picking on you, but my last few subtle attempts to get your attention didn't have the desired effect of opening up a dialog. Glad we can clear it up and get it out of the way ;-) If you read the question (and just the question) and your answer, hopefully you'll see why I felt I had to say something - I found it frustrating because it's clear you have the answers, but you're drowning them out with all the other stuff, and I fear that newcomers will be really confused by it, that was all ;-)

Well, I disagree. A backend cannot replace a SPA built on a JS framework (not to name any). JS frameworks are a lot more than hipster startup work. They bring snappy responsiveness, extremely fast websites. In a world where a 500ms can mean millions of dollars in revenue, a SPA JS solution is the answer.

Search Hashnode