Personally I doubt I’ll ever reach the switching point. But the trend for PHP devs seems to be switching to Go (when they do switch).
Personally I doubt I’ll ever reach the switching point. But the trend for PHP devs seems to be switching to Go (when they do switch).
I don’t have a favourite new feature, but I’m just learning about the Compound constraint which I’ll definitely put to use in the near future.
I do have a favourite deprecation, of Removing the Default Garbage Collector Probability option. I’ve had weird and spaced out crashes when developing before I knew about this. Apparently this is to remove stale sessions once in a while. According to this comment, Debian based distros already handle it cleanly with a cron job, so I just unset that Symfony setting
As long as optional parameters are placed last, I don’t see why not.
PHP8’s named parameters lessen the pain of using a function with optional parameters spread around, but I still stick to that rule.
This one in South Korea is pretty recent (October 2022).
A special police team conducted an investigation of the disaster within a few days of it occurring, and concluded on 13 January 2023 that the police and governments’ failure to adequately prepare for the crowds, despite a number of ignored warnings, was the cause of the incident.
The point is evaluating your stack once in a while. Eventually, you may need to switch or it may be worthwhile, even if you can stick with your current stack at a disadvantage.
For an extreme example, WordPress with crap page builders. It may not have been “that bad” when you started with it. But by now its very much worthwhile to switch. You don’t “need to”, but you should.
Back to this post, maybe they really are at that point that slowly switching is worthwhile. At least partially, where it makes the most sense (they mention using some microservices written in Go).