3 ms·
I think a text-based, declarative rendering API is the right choice. This approach has been vindicated on the web. But the actual implementation of SwiftUI is
by cageface 2y ago
I think a text-based, declarative rendering API is the right choice. This approach has been vindicated on the web.
But the actual implementation of SwiftUI is terrible. Long compilation times, cryptic compiler error messages, bad performance, and a baked-in two-way binding observable state API that's great for code snippets and WWDC talks but makes building a coherent state model in a real app very difficult add up to a big mess.
- deleted 2y ago[deleted]