4 ms·
There are some advantages to this approach that often go unmentioned. Native widgets often have ad-hoc limitations based on their legacy, for example limits on
by willtim 7y ago
There are some advantages to this approach that often go unmentioned. Native widgets often have ad-hoc limitations based on their legacy, for example limits on composing/nesting widgets (can a list box contain a list of arbitrary widgets?) and system resource limits (e.g. windows handles). Attempting to build a cross-platform UI that maps to different legacy systems each with their own quirks and limitations, will never produce something better than QT or Flutter IMHO.
- saagarjha 7y agoYou’re right, I think this is the first time I’ve heard someone mention this. I was actually quite surprised when SwiftUI came out because in Cocoa/Cocoa Touch there is a clear set of things you “can” do and everything else would just break and the new declarative language allows (and even encourages) very strange combinations. I haven’t used it a whole lot, but it seems like they’ve done a pretty good job making it mostly work.