Baldur Bjarnason

... works as a web developer in Hveragerði, Iceland, and writes about the web, digital publishing, and web/product development

These are his notes

@tmj Bringing over iOS apps to macOS hastens the demise of native apps as writing one app for both iOS and macOS will be much more compelling for Swift/Objective-C devs than just making a macOS app.

OTOH, if they wanted to react to Electron in a way that improved macOS as a desktop OS, they could have adopted a two-pronged strategy:

  1. Build a Electron-a-like for macOS out of WebKit and node that performs better, has improved accessibility, uses the built-in WebView, and has more hooks for native macOS behaviour.
  2. Improve Electron to have better accessibility and more native features.

Bringing iOS apps to macOS is only the right response to Electron if your primary focus is iOS and macOS is only a secondary concern.

(IMHO, and all that.)