> underlying framework/runtime can generate the appropriate UI for the exact target platform
This may seem like a good idea, but it's not. What you will get is a leaky, lowest common denominator API that will break on each new OS version.
I don't understand how you got to this conclusion.
I worked on Xamarin app and saw how things worked there. I also think that it's a logical conclusion from these conditions:
1. You want to support N native platforms. 2. Each of these platforms has it's own way of doing this, bugs, etc. 3. Each of these platforms is being actively developed. 4. There are differences between those platforms. One doesn't have guassian blur, the other one doesn't have right-to-left languages.
Re:Flutter looks good, but is painful
by s_y_n_t_a_x on Monday August 05, 2019 @01:06PM
(#20615827)
RN is more flexible. And you can always contribute or build your own native extension to use.
Re:Flutter looks good, but is painful
by alex_suzuki on Monday August 05, 2019 @06:41AM
(#20612931)
Well put.
Yeah, that's true. I'm looking forwards to React Native (AFAIK it uses the native JS engine + native toolkits) and libui.
I'm also hoping for declarative UI frameworks like SwiftUI so that the underlying framework/runtime can generate the appropriate UI for the exact target platform.