Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Are you tracking warnings/deprecations in logs? Usually PHP gives ample warning time (at least one major version) before producing errors.


I tracked the warnings and I keep up with changes out of necessity. But that's the least they can do - anything else would be insanity. However it does not make me feel any better when debugging version/compatibility/configuration issues between the language, different libraries and the environment.

I'm not saying there aren't good reasons for _some_ of the changes, including historical error prone baggage. I'm also not in any way try to disrespect the maintainers. But to say PHP is a stable language and ecosystem still does not reflect my experience with it.


A good test suite does wonders, too.


The tests are there to give us confidence about _our_ code. They can help in those situations, but they don't protect us from others pulling the rug from under us.


Unless you're upgrading production before lower environments, you'll still find out exactly what you need to fix, won't you? And unless you're waiting until the last possible moment to upgrade core infrastructure I don't see how anyone is getting any rug pulled out from anywhere.


Again, seeing what will be broken is the baseline expectation. My comment is not about that. It’s about breaking changes, having to resolve them, facing incompatible versions (language, libs, tooling).

You telling me you broke my code in advance doesn’t make it OK.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: