@agiletortoise @gruber why isn’t it?
I mean, why isn’t it a PWA, that just runs in Safari?
@gruber @stroughtonsmith They also end up in compressed memory (essentially paged out) or evicted entirely from memory with only a screenshot of the screen remaining (so you see something in the app switcher).
Most apps are written to take that into account, but on macOS, the model is different and an app's state is much more visible than the app switcher: it would be weird if the News app just randomly disappeared from the Dock, for example.
@gruber @stroughtonsmith the tooling issues on iOS make this worse too: you can’t run `leaks` on device like you can on the Mac, so finding leaks is either Instruments (also known flaky) or… you just don’t.
(Irony is it should be easy to find iOS leaks via a catalyst build bc you have the full Mac system accessible! Such an escape valve.)
@helge @gruber …how do you personally define native? Because virtually the entire OS is Objective-C/Cocoa, so if you're writing Swift code it's all 'non-native’ 😅 That's a bolt-on runtime with a translation layer and non-native idioms.
If it emits native code, talks to the same system frameworks, and is used to build the system apps, it's ‘native’.