I really like Swift. When the initial versions of Swift became available, I remember still using Objective-C due to the language being in flux and requiring frequent migrations from a previous version to the current version.
At this point, this migration process has slowed down: the language feels mature to me; it has been around for six years by now.
The ABI is now declared stable for Swift 5 on Apple platforms. As a result, the Swift libraries are now incorporated into every macOS, iOS, tvOS, and watchOS release going forward. Your apps will be easier to build and smaller because they won’t have to include those libraries.
A month or two ago, I started maintaining a few Anki decks with the sole goal of making myself memorize things better. In order to enhance my skills, I’m slowly building up a personal knowledge base filled with fundamentals (that I memorize) about certain programming languages.
Fundamentals in this context does not mean pure basics; it means core language understanding as well as what cool things you can do with said language. Another thing I’m doing is going through design patterns again, and putting those in my decks as well.
My initial focus has been Swift language fundamentals since I’m working on various Swift projects right now, but I’ll be doing the same for JS, PHP, and more. There’s so much to learn, but the foundation is usually a good place to start.
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.