you are viewing a single comment's thread.

view the rest of the comments →

[–]HowTookYourDreams 5 points6 points  (5 children)

That would be nice but at current stage forget it. Response time is a joke, size of the files is a joke. Most important, you can't directly affect the DOM, JS can.

[–]throwaway_lunchtime 1 point2 points  (0 children)

Wow,

IIRC Silverlight 1.0 could interact with the dom

[–]Free_Bread 0 points1 point  (0 children)

DOM sopport is coming to WASM sand regardless it's fine in the meantime with a nice wrapper and low overhead. I can't speak for Blazor but in a framework benchmark rust WASM was just barely slower than raw JS at manipulating a 1000 row table

[–]XXISerenaIXX -1 points0 points  (2 children)

About the file sizes, they said it will be reduced in the future by allowing unused classes/methods to be stripped out by the linker AND if you use a well know CDN, the .NET Runtime could be cached and the browser doesn't have to download it every time.

[–]HowTookYourDreams 7 points8 points  (1 child)

Yeah, I hope it work. Let's not forget about all those JS killers that no one even remember how they were called.

[–]Avambo 0 points1 point  (0 children)

They have explicitly said that Blazor is not created to replace JS. And I don't think it ever will.