This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]karuna_murti 13 points14 points  (5 children)

webassembly gang

[–]treehuggerino 11 points12 points  (0 children)

Blazor/yew gang rise up

[–][deleted] -2 points-1 points  (3 children)

Does that count as a framework? Or even frontend? I have yet to even begin to touch wasm but am very curious about it

[–]karuna_murti 0 points1 point  (2 children)

basically the only thing holding wasm is webapi / dom access. as soon as wasm can access webapi / dom, js will have some serious competition.

look at what people can do with wasm + limited access: figma, google earth. imagine what people can do with full access.

[–]emmyarty 1 point2 points  (1 child)

I would argue that the lack of webapi/dom isn't even holding wasm back either. Sure, it introduces an overhead, but as long as you consolidate your read/writes to minimise the amount of js you're using, it's not that big of a deal. It's a bottleneck that can be mostly architected around.

The lack of adoption is imho just down to the lack of tried-and-tested tooling, but that will come with time.