Sean Hollister, writing for The Verge (gift link):

Since the Magnavox Odyssey came out in 1972, game consoles have been built with the same basic goal: to effortlessly play proprietary games on a TV screen. Nintendo, Sony, and Microsoft have spent decades essentially selling the same product. A few consoles could do more, but the formula you know and love remains buy box, plug into TV, insert game, play.

The Steam Machine aims to be something bigger. It’s a vision of a box with fewer restrictions and an almost endless catalog of games — for those willing to spend nearly twice the price of a PlayStation 5.

That’s right. Today, Valve has announced the Steam Machine will start at $1,049 without a gamepad or $1,128 bundled with one, but you aren’t getting a significant boost in performance over the 5.5-year-old Sony PS5 you can still buy today. Even after three price hikes, a vanilla $650 PS5 offers sharper images in Cyberpunk 2077 and Horizon Zero Dawn Remastered in my tests. So how can Valve possibly charge over a grand, you might ask?

It’s because the Steam Machine is, let’s say, a PC-plus. It’s a PC that acts more like a console than any you’ve used before. It’s incredibly cool and quiet, so much smaller than a PS5, surprisingly smooth, and completely navigable with any modern gamepad you own. You don’t need a mouse, keyboard, or even Valve’s own touchpad-equipped Steam Controller to download, launch, or play games. Joysticks do the job.

The price is eye-opening, but that’s the theme across all consumer hardware this year. It’s hard not to root for Valve with its expanding hardware ambitions, but Hollister’s review shows just how far they have to go to achieve “plug it in, insert game, play” simplicity.

This is going to sound cornier than a bucket of Jiffy-Pop, but it is a profound irony that a man with such a big and beautiful figurative heart could have such a lousy literal one.

Apple, in a statement issues to the press yesterday, quoted fully by MacRumors:

The consumer electronics industry is facing an unprecedented challenge. The rapid expansion of AI data centers has created an extraordinary surge in demand for memory and storage. We have never seen a component price increase this much, this quickly. We have shielded our customers from these increases so far, but we have now reached a point where we need to begin raising prices on a number of products, including today’s increases for iPad and Mac. We know this is not welcome news, and we are working tirelessly to find solutions.

I saw a few other publications quote a sentence or two from the statement, but I like to see the whole thing. It’s not long.

Via MacRumors’s Buyer Guide, the current third-gen Apple TV 4K models were introduced in October 2022, and sport the A15 Bionic chip that debuted with the iPhones 13 in 2021. It’s widely believed that new hardware models are coming this fall. I mentioned yesterday that the steep price increases ($130 → $200 for the 64 GB base model; $150 → $250 for the 128 GB model with Ethernet and Thread networking) move Apple TV further out of line compared to the discount set-top boxes and sticks from companies like Roku and Amazon. But even setting aside the prices of competing devices, it just feels wrong to hike prices this much for four-year-old hardware running five-year-old pre-AI silicon. The higher-end model’s price went up 67 percent!

The only way this makes sense is if these prices are really meant for the upcoming new hardware, and those new models are more ambitious home hubs that warrant $200–250 prices. This makes the current models a really bad deal for the next few months, but come September or October, Apple can introduce next-gen Apple Intelligence-ready Apple TV hardware and the prices can remain $200/250. It’s Apple, so maybe the new hardware will have prices that are even higher, and these increases are just stop-gaps to ease the eventual sticker shock upon the new hardware’s reveal.

But as things stand today, no platform in Apple’s portfolio came out of these price increases looking worse than Apple TV. It’s especially painful to think about people buying one now, at these prices, only to have their purchase obsoleted in September or October.

On the eve of WWDC, in a post arguing that “SwiftUI Only Makes It Easy to Develop Bad Apps”, I wrote about an atrocious bug in Apple’s Journal app:

If you’re running MacOS 26 Tahoe, open Journal and make a new dummy entry. Type something like “The quick brown fox.” Then double-click on the word “brown” and delete it. Now invoke Undo.

What you expect is for the word “brown” to reappear. What happens is ... the whole sentence disappears. Gone. Invoke Redo and you only get back to “The quick fox.” The word “brown” is just gone forever. It’s nowhere in the Undo stack. That’s just profoundly fucked up. I’ve never seen anything like this with an AppKit app, ever. (I’ve never seen it with a UIKit app either — and the same thing happens on iOS with Journal. It’s just that you notice it less often because we don’t invoke Undo and Redo nearly as often there.)

Marcin Wichary, linking to my post from his remarkably good, remarkably prolific blog Unsung, wrote:

Software engineering typically has some categories of bugs and failures that result in immediate action — a night shift, a war room, “sevs,” and so on. Those are, in my experience, things like:

• the app crashes,
• the site doesn’t load,
• there is data loss.

Depending on what you work on, this list will also likely include security problems, regulatory considerations, privacy-leaking bugs, and so on. In a more mature organization, these are all well documented, but even in early startups there is some shared understanding that some bugs are bigger than life and they take immense priority over pretty much anything else.

At any company, a version of this list needs to exist for front-end and user-experience problems, and undo should be on top of that list. If you break undo, you drop what you’re doing to fix it.

This seems to be what exactly happened. I don’t understand how Journal’s data-destroying Undo bug persisted as long as it did, but after I wrote about it two weeks ago, I heard from Apple PR that:

• The text editing component in Journal is in fact UIKit, not SwiftUI, so I was wrong to blame SwiftUI just because Journal is largely SwiftUI-based.
• The bug had been identified and fixed for a future update.

Well, the future is already here, because the buggy Undo behavior in Journal is fixed in developer beta 2 on both MacOS and iOS 27. Nice. I hope it gets fixed for the 26.6 releases too, but at the moment it’s still broken in the current developer beta of 26.6 (and, of course, still broken in all the v26.5 OSes). So be careful while writing in Journal.