We borrowed some #PHP code from #StackOverflow that had nested ternaries without parenthesis. Turns out that as a fatal error in PHP 8 on our production server but not on the earlier PHP on our development server. Wow... a language with breaking syntax changes. I'll stick with sound #Clojure, where you never have too few parenthesis.
@worldsendless
PHP had some flaws and problems so it was simply necessary to do a radical change at some point. Everything has been announced in advance, and there's always been a "deprecated" flag in advance to warn programmers. It's just like it is, I'm glad the PHP team finally released #PHP 8 where almost everything behaves like expected (and now the language is far better than #JavaScript, IMHO).
The Packagist ecosystem is vastly more robust and reliable than npm/yarn/whatever.
Oth still have warts from their youth, and both have improved dramatically in the last decade. But I'd still rather work in PHP than JS most of the time for the type system alone.
@worldsendless@kevin@arnan And were even broken in earlier PHP versions, because the default grouping logic was backward from literally every other language that has ternaries. 🙂 That's why it changed to make the () required, so that the language could transition to a more sensible grouping over time.
@Crell@worldsendless@kevin yea I was gonna say, isn't that change just a move toward better structure and usability that has been ongoing since php 5 or so? Take out ambiguity and loose code standards and such ...
@arnan@worldsendless@kevin Yes, PHP has been on a decade long effort to fix all the dumb mistakes made in the 90s. Some of that cannot be done without some degree of breakage, but the internals team tries very hard to make it small and gradual as much as possible.
@Crell No kidding! It's had an open ticket to match their versions for months now, but upgrading the PHP version on shared servers is complicated. I definitely miss our solid Clojure setups.
Add comment