I read some comments saying they use PHP7, latest nodejs, latest framework for whatever in production. Really? Am I the only one stuck with using ancient versions because of company policy?

i do use es6 for javascript, but only because node compiles it back to es5. however php7 is also off the table because of the company. i did get them to update to php5.6 from 5.4! that's a big step ^^

Hhmmm. I'm intersted to know why they don't want to upgrade? We upgraded our infrastructure ages ago and nothing ever broke when it came to PHP compatibility.

Plus, you can easily implement a php version switcher. Even on IIS

In some projects we still have to support IE9, even IE8. I've been using ES6 transpiled to ES5 with Babel.
As for server side languages, I tend to not use the newest version because servers won't always be upgraded and then it's a pain in the ass.

@Skipp same reason @RinseRepeat said. our servers are not the main problem. Many times a client has an existing server they want to keep and those are usually outdated. JS tou can easly compile back with Babel, php is sadly another story.

developers can dictate terms, like we develop code that runs in our servers, put it anywhere else and we don't support it, combine that with automated deployments, automated server builds, and supporting the latest software is a lot easier.

@ThomasRedstone we can dictate terms? We can advise, but at the end of the day, clients and budgets dictate terms.

@rinserepeat nope, developers can set the terms under which they work, some clients might resist, some might leave, but quality clients tend to accept reasonable terms, like the developers who are responsible for the availability of the application controlling the environment the application runs on.