3 ms·
Because, suprisingly, Noone is forcing you to update immediately! Hell, there's still a lot of 5.x deployments out there that work just fine. I even manage one
by tehbeard 5y ago
Because, suprisingly, Noone is forcing you to update immediately!
Hell, there's still a lot of 5.x deployments out there that work just fine. I even manage one or two (both of them being very old, legacy installations in enterprises. In both cases I'm making slow and steady progress to getting them up to 7.x or 8.x so that we can benefit from engine improvements etc).
> Why would anyone in their right mind use a language ecosystem where each major version upgrade breaks their code
That. Is. The. Entire. Point. Of. Major. Versions.
A big red warning and culutral understanding of "stuff we said would be gone, that we gave you a year+ of notice on, is now gone, go read the migration notes if you've been sleeping under a rock."
You act like this is happening monthly? 8.0 came out in Nov 2020... , 7.0 was Dec 2015.
> I just don't understand why people accept this from their tools.
Actually our tooling is pretty nice. Between psalm, phpcs and rector, we have tooling that can forwarn of deprecations in use, and most of the time fix them automatically.
Should you always use PHP? No. But the debate on the nuances as to when to not use it doesn't tend to go well with those who just throw everything out the pram acting like PHP developers are insane because it's not a haskell/rust docker project.
- inoop 5y ago> Because, suprisingly, Noone is forcing you to update immediately! Excuse me, where do you work? Do you not have a company policy about not using software that isn't actively receiving security updates?
- 9dev 5y agoPHP releases receive three years of updates :)
- inoop 5y agoYou said: > Hell, there's still a lot of 5.x deployments out there that work just fine. forgive my ignorance but I was under the impression 5.x isn't actively maintained anymore?
- tehbeard 5y agoOh our company is fully on 7.x and looking to move existing projects to 8.x. (New ones being deployed to 8.x already) The enterprise client is the one on 5.x (for an interop program for B2B order processing), in a secured intranet system behind firewalls (multiple, on occasion one of their teams breaks one while updating it and we lose access for a day) and a VPN. They might get up to 7.x this year when they retire the server "our" VM within there is on and reprovision to some new metal. But by all means, go try and bypass their procurement and change process. I'm sure they'll appreciate your insight into rapidly changing a component of one of their main revenue streams... Just let me grab some popcorn first :) To be a little less cutting, its admirable to want to be clean and proper, to do it all the right way 100% of the time... But that ain't how the world works and you either bend to accommodate and try to do some good, or scream into the digital void... Your choice.