Aspnetcore: Blazor development depending on WebAssembly progress ?
Hi
if one looks at http://webassembly.org/docs/future-features/ or https://wasm.news it is for the layman difficult to see, if there is real progress after mvp.
Since I am not an expert in these matters at all I wonder:
Does the Blazor group know what the state of these developments is, maybe even contributing to it?
Is future Blazor development or its finalisation as a real product dependent on wasm being developed further?
How do you assess the risk, if wasm stagnates or even looses general interest as a consequence of no visible further developement.
Very interested to hear Your take on that. Even if I misjudge the situation completely.
Thanks for info
Cheers,Michael
michaelongithub
All 3 comments
Various folks from the .NET team and Mono team are participating in the WebAssembly group on new features and enhancements. Some of these features would help improve the experience of running .NET in the browser. However, we don't believe Blazor is blocked on any of these additions - we can have a good experience with only the existing WebAssembly support.
danroth27
on 19 Apr 2018
@michaelongithub Do you know this video on the future of WASM? I found it quite interesting.
rstropek
on 20 Apr 2018
thanks, for the hint, very interesting.
michaelongithub
on 20 Apr 2018
Related issues
markrendle
路
3Comments
rynowak
路
3Comments
snebjorn
路
3Comments
ipinak
路
3Comments
Kevenvz
路
3Comments
Most helpful comment
Various folks from the .NET team and Mono team are participating in the WebAssembly group on new features and enhancements. Some of these features would help improve the experience of running .NET in the browser. However, we don't believe Blazor is blocked on any of these additions - we can have a good experience with only the existing WebAssembly support.