3 ms·
I wonder what’s exactly preventing them from implementing UIKit on macOS, that necessitates running the app in a simulated iOS environment... The biggest pain
by aaaaaaaaaab 8y ago
I wonder what’s exactly preventing them from implementing UIKit on macOS, that necessitates running the app in a simulated iOS environment...
The biggest pain point on macOS is the crappy AppKit framework which has so many awful quirks due to legacy reasons (e.g. layer-backed vs non-layer-backed views, no standard collectionview, etc.).
- manmal 8y agoMy understanding was that they did implement UIKit on macOS, but that there are still limiting factors that force them to wrap them up in a VM (which will most likely change until next year).
- scarface74 8y agoThere is no VM. Even the iOS simulator for iOS development is not a VM. When you run your code in the simulator, it’s compiled for x86 and linked against an x86 version of the iOS framework.
- manmal 8y agoI know, I‘m a iOS dev. Some Marzipan apps reportedly are wrapped in a VM now. Haven’t checked myself.
- dbbk 8y agoThere is no simulated iOS environment here.
- saagarjha 8y ago> layer-backed vs non-layer-backed views Most views are layer-backed by default these days. The newer APIs tend to "force" this decision on you by doing things like making your entire view hierarchy implicitly layer-backed in many cases to encourage layer-backing. > no standard collectionview NSCollectionView?
- aaaaaaaaaab 8y agoYeah, I’ve heard that NSCollectionView got revamped in El Capitan or something, haven’t really checked it since then.