I bought a MacBook Air M3 for Vision Pro development and made it my main machine

I had done Vision Pro development outside several times, and since my only Apple silicon Mac was a Mac mini, I had been carrying it around together with an external monitor. That activity has finally come to an end.

Before Vision Pro was released in Japan, I still wanted to touch Vision Pro development somehow, so I bought a Mac mini for the lowest possible cost and started developing.

After that, I bought Vision Pro and took it out with me to various places. That made it very clear that carrying a Mac mini around is, as expected, extremely troublesome. That dissatisfaction grew day by day, until one day it finally exploded.

In other words, I bought a MacBook Air.

If I was going to buy one, I wanted a good one. But even a good one should ideally stay under 300,000 yen to avoid the hassle of depreciation as a sole proprietor. So I chose specs that were just barely below that. The memory is 24GB, and the storage is 1TB.

When I previously bought a 12-inch MacBook, I chose a JIS keyboard and deeply regretted it, so this time I chose a US layout. I hereby swear that I will probably never buy a JIS-layout PC again.

The MacBook Air I purchased was prepared in Shanghai and arrived in my hands after nearly a week. I did several setup steps and made it usable for work. Actually, setup is still in progress, and it will take a little more time before the Vision Pro development environment is fully ready.

If the only reason was wanting to develop for Vision Pro outside, it might not seem necessary to make it my main machine. But that is not how it works for me. When I decide to focus on something, I tend to immerse myself in that environment.

That is why I began wanting to write backend code in Swift as well and started introducing Vapor and related tools. It is not that I dislike Windows, but at least privately, I felt I could not move forward unless I temporarily said goodbye to Windows.

Writing it this way may make it sound like I have become someone who wants to write absolutely everything in Swift, but that is not the case. For work, JavaScript / TypeScript is still my main language for both frontend and backend, and I also work in Windows environments.

However, for my private projects, I plan to move everything toward Swift. I plan to build apps with Xcode and Reality Composer Pro rather than Unity, and maybe I will even make this site Swift-based.