3 ms·
Having a scripting layer is ok-ish, but then you can't use your native lang (swift, .net/xamarin, java, etc). So this mean that to have "cross-platform UIs" yo
by mamcx 9y ago
Having a scripting layer is ok-ish, but then you can't use your native lang (swift, .net/xamarin, java, etc).
So this mean that to have "cross-platform UIs" you MUST commit to a inferior language glue. Js is bad, Dart is better, but Swift/C#/F# is WAY better.
- filiph 9y agoJust a note: one of Flutter's differentiators is that renders every pixel, straight to OpenGL / Vulkan. It doesn't do cross-platform the way RN or Xamarin does it. It's more like Unity. Since most featured mobile apps nowadays have very custom UIs, we hypothesize that this is a very important feature going forward.
- s73v3r_ 9y agoMost featured mobile apps are still using the native widgets. They're just styling them.
- mamcx 9y agoThis part I could agree, and for most of my apps make a lot of sense. I download the code and run the sample where is possible to integrate flutter with the "host" language. Is better than react native, but I wish it have a more ergonomic api.
- nikki93 9y agoDart compiles to machine code plus the rendering is mostly impl’d in Dart so you can change basic things about the rendering in Dart, FWIW. In general the dichotomy you’re painting b/w scripting and native languages can hold, but the details make the difference. One interesting thing in this case is having a single language that AOTs but also JITs. The hard thing is re: interfacing to platform APIs, which the OS usually provides in its blessed lang (Java / Obj-C).