3 ms·

That statement applies equally to any web-based framework, any native framework, Java, appkit, UWP, Silverlight… Apple could have invested in SwiftUI on Mac to

by n8cpdx 4y ago

That statement applies equally to any web-based framework, any native framework, Java, appkit, UWP, Silverlight… Apple could have invested in SwiftUI on Mac to the same extent they did on iOS, and things would look very different. SwiftUI as currently implemented on Mac breaks enough platform conventions and is, relative to existing native UI, slow and buggy enough to IMO not more native than any other cross platform UI solution.

galad87 4y ago
Which UI conventions are broken? SwiftUI mostly uses the standard AppKit widgets, then it's up to the developer to use it or to customise everything and make a monster out of it. The main "issue" is that it's much easier to customise things in SwiftUI.
GeekyBear 4y ago
> That statement applies equally to any web-based framework, any native framework, Java, appkit, UWP, Silverlight… Except for the part where Apple doesn't hype and then quickly abandon developer APIs the way some other companies do. AppKit, for instance, has been continually iterated on for three decades now. Since Apple has been very clear that SwiftUI is "where the puck is going", I doubt it will be abandoned as quickly as Google or Microsoft's "future of platform development strategy" of the month.