Hacker News Reader

Comment by originalvichy | Hacker News Reader

I wonder what this will do to Electron. If the iOS apps are really 1:1 on macOS, then the need to maintain an electron app will probably diminish. As long as they both support the same OS APIs I can see devs that can learn a new language (Swift) ditch Electron.

View on HN

Apple had a list at the State of the Union of open source technology projects they had built pull requests for to add ARM support. Electron was up there, as was Python 3, OpenJDK and Go, notably.

Would love a link to that if you still have it on hand.

Electron already has support for ARM64, but no official releases yet. But it needs to be build from x86 machine. No native compilation on ARM64 yet. I think with apple moving to ARM, google will add native ARM64 compilation for chromium. This in turn will be picked by electron. Chromium has been running on ARM for a long time with Android and Chrome OS so it has all the optimizations.

But if you're developing with Electron, the purpose is typically cross platform desktop support. This won't change that?

I'd wager for a significant amount of shops it's less about cross-platform support and more for being able to throw existing generalist or web frontend developers into native development. If a business wants to ship a desktop app quickly, it's hard to argue against electron because your existing teams can become productive without too much training.

Mac and iOS aren't the only two platforms.

Hrmn. Wouldn't this be leaving out android and windows? It might be practical for some apps, but that's an awful lot of users.

Is there anyone building on Electron and only targeting the Mac desktop environment? Windows is still the king there.

Is MS Teams for Windows written with Electron? It is on Mac.

Yes it's Electron.

The processor architecture is not that relevant if you are working at the abstraction level that electron or swift-ui or similar provides.

Isn't this already the case?

iOS apps can be built, for Intel, using Catalyst, with very trivial changes in code, but we still see Electron hanging around today like a bad smell.

I can't imagine this will change anything.

Catalyst and SwiftUI are (were?) very immature technologies, not yet ideal for production software. I'd imagine that we're at least a year out from seeing real SwiftUI software in the wild.

But have you actually used a Catalyst app on mac? They're terrible ports as it is right now.

Eh, Catalyst apps are as good or bad as the developer wants them to be. Voice Memos and "Find My" on the Mac are two fantastic Catalyst apps, and certainly better than Electron.

Anyways Catalyst won't even be relevant in the long term, once iPhone apps are written in SwiftUI

Interestingly there's a few mentions of Catalyst improvements in the Xcode 12 release notes:

> When bringing iPad apps to macOS, you can now use the Optimize Interface for Mac target setting to use native macOS controls and Mac resolution

Hopefully this means Catalyst apps will feel a little more like actual Mac apps.

As bad as Electron? I think not.

I often close the Twitter app and Apple's news and stock apps on my Mac mini because the performance is terrible. Hoping they've spent time tuning this more.

I am soo much looking forward to using native Slack and Teams instead of their horrendous electron apps, that even don't use GPU acceleration on iGPU Macbooks!

Reply on news.ycombinator.com