justin․searls․co

Wayne Ma and Qianer Liu say we'll have to wait to see a sequel to iPhone Air, but The Information provides literally nothing beyond this headline outside their paywall:

Apple Delays Release of Next iPhone Air Amid Weak Sales

But does one truly need to fork over $399 to know exactly what the body of the article is going to say?

All you need to know is that Justin Searls loving an Apple product is effectively the kiss of death in the Tim Cook era:

2015: 12" MacBook, my all-time favorite Mac, cancelled after two revisions
2018: HomePod, of which I bought six at launch, never sold through its initial manufacturing run
2020: iPhone mini, my all-time favorite iPhone, cancelled after one revision
2024: Vision Pro, which I rely on daily, received one revision under duress
2025: iPhone Air, which is exactly what I asked for, had even its one revision cancelled

I don't know what I'm doing wrong here.

I've been using Tahoe since July and I've really, really tried to like the new Spotlight because I'm encouraged by the direction it's taking, but I'm giving up and going back to Raycast. It's just WAY TOO SLOW.

If you set up quick keys and then type them "too fast," it'll always do something else instead. Same goes for launching apps by name. Just typed "1p", but Spotlight spent 3 seconds assuming that meant I wanted to open a product page for a Ring camera in Safari.

Copied!

My bro's staying with us, and he's pointed out what a mess our home network is. Spent all weekend detangling a rat's nest of overtorqued ethernet cables, and it's still busted. I feel awful about it.

Kink shaming isn't cool.

Copied!
Breaking Change artwork

v46 - Adjusted Gross Intelligence

Breaking Change

Video of this episode is up on YouTube:

I'm back and I'm angry. My power went out, which caused my Internet to go down, which broke my favorite mug. And that's just the shit that happened before 7 AM. By 9 AM my doorbell was continuously chiming for no fucking reason.

Join me in the struggle. We shall persevere. Tell me how your morning went by writing in to: podcast@searls.co.

Here 4 U:

Fantastic write-up by Nowfal comparing AI's current moment to the Internet's dial-up era. This bit in particular points to a cleavage that far too few people understand:

Software presents an even more interesting question. How many apps do you need? What about software that generates applications on demand, that creates entire software ecosystems autonomously? Until now, handcrafted software was the constraint. Expensive software engineers and their our labor costs limited what companies could afford to build. Automation changes this equation by making those engineers far more productive. Both consumer and enterprise software markets suggest significant unmet demand because businesses have consistently left projects unbuilt. They couldn't justify the development costs or had to allocate limited resources to their top priority projects. I saw this firsthand at Amazon. Thousands of ideas went unfunded not because they lacked business value, but because of the lack of engineering resources to build them. If AI can produce software at a fraction of the cost, that unleashes enormous latent demand. The key question then is if and when that demand will saturate.

Two things are simultaneously true:

  1. The creation of custom software has been supply-constrained throughout the entire history of computing. Nobody knows how many apps were never even imagined—much less developed—due to this constraint, but it's probably fair to say there's an unbelievably massive, decades-long backlog of unmet demand for custom software
  2. We aren't even six months into the Shovelware era of coding agents. Exceedingly few developers have even tried these things; the tooling is so bad as to be counterproductive to the task; and yet experienced early adopters (like me) have concluded today's mediocre agents are already substantially better at writing software

It's long been my view that the appropriate response to the current moment is to ride this walrus and leverage coding agents to increase the scope of our ambitions. By the time software demand has been saturated and put us out of jobs, the supply of programmers will already have tapered off as the next generation sees the inflection point coming.

In the short term, the only programmers actually losing their jobs to "AI" are those who refuse to engage with the technology. Using coding agents effectively is a learned skill like any other—and if you don't keep your skills current, fewer people will want to hire you.

Watching Becky explore the world of bodybuilding, all I know is I would really struggle with my body being scrutinized by others. Surprisingly, though, I'm actually most impressed with the vegan bodybuilders—somehow they all seem to maintain a really healthy self-esteem. Maybe it's because they never whey themselves.

Copied!

How to downgrade Vision Pro

For stupid reasons, I had to downgrade my Vision Pro from visionOS 26.1 to 26.0.1 today. Here's how to put Vision Pro into Device Firmware Update ("DFU") mode and downgrade.

Here's how to restore a Vision Pro in 9 easy steps:

  1. Buy a Developer Strap for $299
  2. Go to ipsw.me and do your best to dodge its shitty ads as you try to download the IPSW restore file for your model Vision Pro at the version you need (if you don't see that version, it's likely because Apple isn't signing it anymore and you're SOL)
  3. Install Apple Configurator to your Mac
  4. Connect the Developer Strap to your Mac via USB-C, and disconnect Vision Pro from power
  5. Get ready to press and hold the top button (not the digital crown, the other one), then reconnect power to Vision Pro and immediately press and hold the top button until the outer screen shows a cable icon
  6. Open Apple Configurator, and you should see a Vision Pro icon.
  7. Drag the IPSW file over the Vision Pro icon and click Restore
  8. Click things and hope it works
  9. Ask yourself what the fuck you did in a past life that brought you to this moment

Good luck, have fun. 🕶️

Breaking Change artwork

v45 - Developer Strap-on

Breaking Change

Video of this episode is up on YouTube:

This may be the version 45 release of Breaking Change, but when you factor in its Hotfixes and Feature Release entries, this is somehow the 50th episode of the show!

Why? Why are we still doing this to ourselves? Write in your answer and how you feel about yourself as a result to podcast@searls.co. Seriously, I need some new material.

The web runs on links, so have some:

Show me them show notes…