After watching a stream where Matt Stauffer and Derick Rethans (the creator of Xdebug) discussed setting up Xdebug with Visual Studio Code, I decided it might be helpful to write a post on setting up Xdebug with PhpStorm, specifically if you’re running Laravel Valet.
This is both for myself for future reference, and for anyone who stumbles upon this post and finds it helpful. Without further ado, let’s get into it.
I’m sure no one is surprised when I was wrong yesterday when I made my predictions about Apple’s new silicon transition. We don’t know anything about what’s going to be the first Mac to receive an Apple Silicon chip, and what I did predict - that there would be no compatibility layer for original apps, was clearly wrong.
Hilariously, Apple showed today that its new computers are going to be capable of doing much better, and I suspect we’ll be quite surprised when we actually see the new devices hit the market later this year (they did promise by the end of the year).
I also wonder about the future of macOS, especially given the new design of macOS and the fact that we’ll be able to run iOS and iPadOS apps on the Mac. Maybe down the line, when this transition is all over, we’ll have an Apple OS instead, capable of running whatever we want.
I’m sure we’ll hear more about this throughout the week, but colour me impressed.
If rumours are to be believed, tomorrow during WWDC, Apple’s annual developer keynote, the company will announce a transition from Intel-powered laptops and desktops to new proprietary chips of their own making.
This should increase performance on these devices (over the equivalent Intel counterpart), as well as allow for the laptop lineup to last longer.
Predictions
I am making the following predictions here (I’m sure we’ll be laughing at some of these tomorrow, but hey):
- First laptop to use ARM will be the MacBook Air
- First desktop to use ARM will be the iMac
- MacBooks will last 50% longer (so the Air would last 15 hours on a single battery charge on ARM)
- No compatibility layer for Intel apps, meaning that all apps would need to be updated for the new architecture
- First available ARM devices coming in the next three months
Over the past few years, I’ve had the displeasure of dealing with various cases of data loss (sometimes accidental, sometimes intentional) that was no big deal because I had backups in place. On the Mac, I’ve been using Time Machine for years, but on Windows my backup system has been a little shaky.
That’s what I’ve been figuring out the past few weeks, and in this post I’d like to discuss my backup strategies.
As far as I’m concerned, there’s three levels of backups. I’ve also included a so-called level zero, where you have no backup. Let’s take you through these scenarios in case your primary storage drive starts failing. (This is a level system of my own making.)
The idea here is that your machine works, except for your hard drive or SSD, which won’t work any longer. Let’s say it doesn’t even get detected any more. This is a common scenario.