Comment Re:Incessant version changes (Score 1) 85
Over the years, PHP has done a more-than-admirable job of mitigating backward compatibility (BC) where possible and documenting everything else really well. If you look at the current PHP-8.0.0 BC page on their website you'll see very detailed description of what breaks. Often times, the changes required that break BC are a result of earlier mistakes that are now being corrected after years of warnings. The other area PHP excels at is documentation.
I've had very little code actually break at upgrade time. Why? Well first, I write good code. Second, I'm mindful of pending upgrades and begin plotting upgrade paths as soon as practicable. I pour of my code to ensure impending BC issues are mitigated pre-upgrade. I have a unit test suite at the ready for upgrade day and make short work of any stray issues. In my 25 years working with PHP, I've never had to stay late after work on upgrade day. Not once.
It's true. PHP's usage numbers have declined somewhat over the years. But "ever more people abandoning the language" hardly suits the facts. PHP powers 8 out of 10 web servers in the world. The fact that it was 8.01 last June is of no concern to anyone not jumping ship. The bulk of your gripes seem to home in on having to work to maintain your code as the language you chose to write it in evolves, matures, advances. It appears as though you got yourself a shiny new toy and threw away your old one. That's okay. And it's okay to jump ship too. Just make sure you bring a life-preserver. And write good code that survives version BC issues. Because all server-side toys, new and old, shiny and dull, have them.