[lambda_lover]

Good point on 1) -- basically, Intel has produced enough problems for a high enough cost that there's reason enough to try alternatives.

On 2)... I hate web apps. Probably much more than your average layperson. Electron is miserable in my experience -- laggy, high memory/CPU user, non-native feel, but I think a web app in a browser is OK. There are really two different use cases I see here. a) Take TurboTax, for instance. I don't want to download a TurboTax app for my computer. I'd only use it once or twice a year. But it works well in a browser. It's complex enough that a web app is justified. b) Spotify. It needs to interact with local files, and I usually have it up in the background. A web app doesn't work well for this. Unfortunately Electron doesn't work well for this either.

I think if this is executed well it could be amazing -- what if layouts scale beautifully onto a laptop screen, so I can use an iOS app instead of an Electron app for Spotify/Slack/etc? If this happened, the benefits could trickle down into iOS, making it a more useful platform. On the other hand, layouts might not scale well for larger screens, and iOS apps on macOS could end up neutered and even less useless than a current webapp. Hopefully the former case happens, but lately Apple makes me feel like the latter is more likely.

3) I'm not really convinced that this will reduce bugs. In my experience, combining two pieces of software into one just makes the resulting monolith harder to reason about because it doubles complexity at high levels and increases complexity exponentially at low levels. But maybe that says something about my development skills :)