Lots of talk about the plan to deprecate dynamic properties in PHP 8.2 and remove them (by default) in PHP 9.0, except when allowed by a special attribute.
It does seem burdensome to project maintainers. And if they are unable to muster the effort to upgrade their packages, it could hinder adoption of PHP 9. It could also harm community relations, with so many maintainers suffering from change fatigue.
But will it?
Ooh, this looks handy: A guide for reconfiguring a Synology NAS to act as a remote Docker host https://qmacro.org/2021/06/12/remote-access-to-docker-on-my-synology-nas/
Hot tip 🔥
If you're passing a lot of arguments to a constructor or method, try to see if you can group them and create a new class/object with the arguments as properties. It'll better describe the domain and provide additional documentation🙂 #php #phpc
P.S. these are called DTOs (Data Transfer Objects) or Value Objects
* read only properties
* first-class callables
But since I'm also not on PHP 8.0 yet, I can also look forward to:
* named parameters
* constructor properties
* nullsafe chaining operator
* match expressions
* static return type
* making the @ suppression operator no longer silence fatals
... and much, much more.
Been hemming and hawing over a hobby project idea since April, and finally made some progress on it today thanks to Miro (mapping out my ideas) and Auth0 (handling signup and login). One detail I need to fill in is how to create a local database record for users that sign up via auth0, so I guess that's my next avenue of inquisition. And then I can get started on the visual design.
@Crell Hey, quick thought on your data provider blog post (which was a great summation of my favourite parts of data providers): a fifth advantage of `yield` over `array` is that if you accidentally give two data provider entries the same name, a `yield` will result in both being tested, but an `array` will result in the second occurrence clobbering the first. It's silly, but for large providers, it could conceivably one day save someone's butt.
Reading GitHub comments on one coworker's PR, another coworker compliments his coding style and advocates for that method of avoiding nested if statements. And I'm like "Yeah. Preach it."
And then I lurch forward, remembering that I wrote one earlier today & have suddenly realized a way to refactor it to remove the nesting.
Do I code now, or do I wait until tomorrow?
Installing PHP 8 on Raspbian is a lot easier when you have a decent guide for it. Found this one tonight: https://lindevs.com/install-php-8-0-on-raspberry-pi/
I finally got my underwater drone back in the water after a long winter hiatus, and I found something neat! https://youtu.be/KT-g50Rq-2o