
Lastly, but most importantly for developers: why bother when you can use var_dump() or Symfony’s dump() or Laravel’s dd()?.Given that when used as part of Laravel’s tinker it boots up the whole app into a REPL environment, does that render something like Xdebug somewhat redundant? I’ve previously written an article () on how superb PsySh is as an application’s command line.

It was a pain trying to set it up manually before, but what about now, where Xdebug runs a server on an IP, but it will be running in Docker? A lot has changed since I started – I use Jetbrains PHPStorm as my IDE, and develop with Docker. Plus, things like custom “bookmark” browser extensions made it feel like you had to jump through a lot of hoops to use it effectively. I’d tried Xdebug before at some point – I can’t recall when, and had an experience that left me thinking that understanding what you could do with it would take far too much time up for me to learn.It’s not like it was some obscure or new tool being talked about. It’s been around years – I started writing PHP professionally in 2016, by which time Xdebug had existed for 14 years.


Quite the controversial “hot-take” from Derick, and while it certainly caused quite the stir (that it was probably designed to), it made me think.
