I wish #PHP had two things and none of them involve generics... I wish it had type aliases and a native base32 encoding/decoding mechanism (in a class or a pair of functions I do not care)
Please, web app developers, consider how your users will upgrade. If your upgrade process is "remove the old one, unzip the new one", then it's not an upgrade process. It's an encouragement to never upgrade.
#PHP folks, what framework-agnostic tooling (as in not #Symfony / #Laravel / #Laminas etc) are you using for running headless browser-based tests these days via something like #PHPUnit?
I'm looking at setting something up in #Docker on #macOS, I've tried Symfony Panther and it's been a shitshow of errors and not being able to get #Chrome or #Firefox running in Docker :/
If the only #PHP I’ve written has been in the course of forcing Wordpress edge cases to work, how would one suggest getting started with #Laravel? (I write a lot of #Javascript but don’t necessarily want to write it on the server).
I am currently thinking about learning new programming language ecosystems and skills.
My current thoughts about #php - can one earn decent money with #php nowadays?
What does the php community say? What learning resources should I check out (for those unaware: I am a professional Rust dev and have >10 years experience in programming - no need for a beginner tutorial).
It's interesting to read an article which criticises the #PHP community-based committee governance model.
Because the argument boils down to 'design by committee rarely achieves excellence'.
But what's missing is, who defines "excellence"? A BDFL might achieve more for their goals, but anyone who wants something else is told 'too bad, so sad'.
PHP is a generalist web language. A governance committee ensures diversity of goals & a more broad evolution of the language.
I am baffled by how much trouble I’m having at writing #rust at a decent clip. #Golang I felt pretty good at after a few months, same with #Python and #PHP. Meanwhile I’ve been trying to write anything useful in Rust for months and it’s so incredibly slow going.
I’m shocked people are enthusiastic about adopting this for their jobs. If I had a specific part of an app that needed more speed, absolutely. But as a general purpose language? I’m not seeing it yet.
I’ll keep ramming my head against it but have not enjoyed myself thus far. If writing a proof of concept in python takes me 4 hours, rewriting that in rust clocks in easily at 12-16 hours.
I can get #PHP’s RecursiveDirectoryIterator working by passing it to RecursiveIteratorIterator and looping over it, like here: https://3v4l.org/ll176
But I can’t seem to figure out how to get this working with RecursiveCallbackFilterIterator. From my understanding, this should have the same output as the example above, but it’s not even looping because $contents->valid() is returning false. https://3v4l.org/MM7kZ
Saw this on the #Laravelshift newsletter (admit I mostly signed up for tips at the bottom), and looks like Jason doesn’t post on Mastodon… yet :) so posting here. Have to admit, I’ve had a hankering for something like a .laravel file a few times now.
The merging of sequences and maps into a single structure in #PHP has cost me many hundreds of hours and innumerable bugs over my career. It is still doing so now.
🆕 blog! “Should the WordPress scheduler use datetime-local?”
There's a brilliant post by WordPress about how they've optimised some of the backend code to make it more efficient. So here's a suggestion for something else which can be optimised. If you want to schedule a blog post to be published later, you have to use this WordPress control: I find it mildly an…
I've got a PHP website with a PostreSQL backend. It's entirely read-only in production, and its largest table has about 10,000 rows. Postgres, PHP, and a Caddy proxy all run in separate Docker containers.
Is it crazy to think that a simple system like this would run just fine with SQLite instead? In the longer term I’d like to move the whole thing to running with the Django Rest Framework and rework the front-end bit entirely.
Proposal for a conference talk: How to configure #PHPStorm and all its tooling extensions (xdebug, phpstan, php-cs-fixer, etc.) to use a docker container consistently.