3 ms·
The strategy is that native macOS UIs are generally easier to develop than native Windows UIs, so they're trying to iterate on that platform first.
by odo1242 4y ago
The strategy is that native macOS UIs are generally easier to develop than native Windows UIs, so they're trying to iterate on that platform first.
- capableweb 4y agoIf they're building a native macOS UI, how is it ever possible it'll be worthwhile to port that into native Windows UI or "native" Linux UI? If you wanna go cross-platform, you usually consider that from the start, not once you're 50% done, as you're gonna have to redo a lot of work you could have gotten "for free".
- EthicalSimilar 4y agoThe “engine” itself is likely cross-platform, with vendor-specific UIs. It’s likely quicker to develop for a single OS and then build the additional UIs with a more feature-complete app.
- imbnwa 4y agoArc browser is also doing this, and they're planning on debuting the Windows UI in Fall.
- saagarjha 4y agoIsn’t the whole selling point behind their thing that they don’t use the native macOS UIs but instead send everything to the GPU?
- shaunsingh 4y agoRendering a platform native GUI and what you render it on are two different things. In the case of Zed, its a combination of - metal is quite easy to work with - apple has clear design guidelines and nice toolkits The Xi editor team quickly found out how much of a mess "native" gui's were on windows. Zed will hopefully add support for vulkan and linux/windows later, but it makes sense to start off on macOS
- saagarjha 4y agoMetal is not a platform native GUI, it is Apple's graphics API. The native UI on the platform is Cocoa (which calls Metal for some things, but isn't being used here).