4 ms·
I suspect that mid term this is going to be changing. There is currently a big behind the scenes push to move the web target to Wasm (dependent upon Wasm GC lan
by mhoad 5y ago
I suspect that mid term this is going to be changing. There is currently a big behind the scenes push to move the web target to Wasm (dependent upon Wasm GC landing in some kind of reasonable timeframe).
At that point I suspect you will see the importance of compiling to JS declining rapidly.
Side note: The other major push that seems relevant to some of the other comments here is they are also looking to redo the shader pipeline from scratch and make that AOT compiled as well because right now it tries to just JIT all of that and it isn’t always very predictable as a result. [1]
So combining that along with a WASM target I actually feel super bright about the future of Flutter as a tech choice on web, desktop, mobile etc…
They have some more detail about both of these things in their Roadmap [2] if you’re interested.
[1] https://github.com/flutter/impeller https://github.com/flutter/impeller
[2] https://github.com/flutter/flutter/wiki/Roadmap https://github.com/flutter/flutter/wiki/Roadmap
- pzo 5y agoI think they are planning to use wasm as target for Web. They don’t have any reason to compile to wasm on mobile when they already can compile to native. WASM is equivalent of JVM and I doubt they will start providing binding to different languages. Even if they do Dart would be the still main language on this platform in similar vein like Java/kotlin is the main language on JVM - JPython, JRuby, Groovy are irrelevant. I also don’t think JavaScript/Typescript will get irrelevant in WASM - for the same reason even though you currently can compile CPython to wasm