Client Side Strategy

[kc]

Good to see a single Product Manager - Tim Sneath - for Dart and Flutter.

The medium article on the MS confused client side strategy was spot on.

Devs are really looking for a joined up strategy from Google with a commitment to deliver. Along three axis:
X - web
Y - mobile
Z - devices - phones tablets ultrabooks nucs tv desktop

Imo the key is to break down the division between web/docs and apps/mobile with a kind of fluid interactive canvas which is secure and network aware. Progressive web apps, Instant apps, Fuchsia - there's a lot going on in this space.

The competition is primarily Kotlin and ReasonML. Also an invigorated ecmascript.

K.

[Anders Sandholm]

Sorry if I missed something, but it is not clear to me how ReasonML addresses high-performance deployment on mobile.

 

K.

--
For other discussions, see https://groups.google.com/a/dartlang.org/

For HOWTO questions, visit http://stackoverflow.com/tags/dart

To file a bug report or feature request, go to http://www.dartbug.com/new
---
You received this message because you are subscribed to the Google Groups "Dart Misc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to misc+uns...@dartlang.org.

--

Anders Sandholm, Product Manager, Dart

[kc]

Decent perf via react native.

Also in the future from the reasonml site:
The ability to render to native code. OCaml's native (assembly) startup time is in single digit milliseconds. We have big plans to use Reason on native one day; meanwhile, we're focusing on adoption through great JavaScript compatibility.

Maybe if wasm gets gc&dom ocaml can skip js. Or even with a native style ui toolkit like Flutter.

K.