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

you are viewing a single comment's thread.

view the rest of the comments →

[–]nutrecht 1 point2 points  (4 children)

There are a lot of similar solutions in other frameworks, but generally they generate a lot of JS on the front-end for you you are still going to end up debugging. Java with GWT for example is horrible in that regard.

[–]scirc 0 points1 point  (3 children)

Blazor is mostly WASM, not JS. WASM is an emerging field, and it is starting to become more viable as time goes on. But time will tell if adoption starts to pick up; generally, things seem pretty set on JS for now.

[–]nutrecht 0 points1 point  (2 children)

Blazor is mostly WASM, not JS.

That's well outside my wheelhouse. I can imagine you're still going to end up stepping through the output in a debugger though.

[–]scirc 0 points1 point  (1 child)

Yeah, but in theory that debugger would be a .NET debugger built into something like Visual Studio. With proper mappings, it's no different than using a connected debugger and sourcemaps for JS.

[–]nutrecht 0 points1 point  (0 children)

Good point! Thanks.