3 ms·

Compared to the Blazor tooling, the Typescript tooling is miles ahead imo. We did a Blazor app during a hackathon and I was pretty frustrated with how inconsist

Compared to the Blazor tooling, the Typescript tooling is miles ahead imo. We did a Blazor app during a hackathon and I was pretty frustrated with how inconsistent the build errors were with blazor components. What makes me most skeptical about Blazor though, is that it's shifting a huge burden to the client just to make developers happy. Even if the runtime is stripped down and compiled to wasm, it seems kinda wild to send a whole runtime just so you can run C# code, especially when there's alternatives like Rust that require no runtime. What's funnier too, is that it's been possible to write F# on the frontend for a while now, compiling down to javascript (like clojurescript). It makes me wonder why this approach was never done with C# too, even if there are pitfalls in compiling to javascript.

jordanab 5y ago
I'm already seeing a lot of enterprise companies gearing-up to go all-in on Blazor. Having a single language (C#) for web, mobile and all other back-end services must be huge draw for them. > What's funnier too, is that it's been possible to write F# on the frontend for a while now, compiling down to javascript (like clojurescript). It makes me wonder why this approach was never done with C# too, even if there are pitfalls in compiling to javascript. There have been several initiatives which allowed you to do that. None of them really successful. I've worked with one specifically in the past (can't remember the project's name though), which even had C# types/bindings for Knockout.js.
marwis 5y ago
There were a quite few independent efforts to bring C#/.NET to the web the proper way (JSIL, SharpKit, WootzJz) but Microsoft was never interested in them and for some reason chose the invest in the worst and most wasteful technical solution.
electroly 5y ago
> Even if the runtime is stripped down and compiled to wasm, it seems kinda wild to send a whole runtime just so you can run C# code FWIW, you seem to be talking about Blazor-WASM, but most real-life Blazor usage right now is server-side Blazor which doesn't do any of that.

jordanab 5y ago

I'm already seeing a lot of enterprise companies gearing-up to go all-in on Blazor. Having a single language (C#) for web, mobile and all other back-end services must be huge draw for them. > What's funnier too, is that it's been possible to write F# on the frontend for a while now, compiling down to javascript (like clojurescript). It makes me wonder why this approach was never done with C# too, even if there are pitfalls in compiling to javascript. There have been several initiatives which allowed you to do that. None of them really successful. I've worked with one specifically in the past (can't remember the project's name though), which even had C# types/bindings for Knockout.js.

marwis 5y ago

There were a quite few independent efforts to bring C#/.NET to the web the proper way (JSIL, SharpKit, WootzJz) but Microsoft was never interested in them and for some reason chose the invest in the worst and most wasteful technical solution.

electroly 5y ago

> Even if the runtime is stripped down and compiled to wasm, it seems kinda wild to send a whole runtime just so you can run C# code FWIW, you seem to be talking about Blazor-WASM, but most real-life Blazor usage right now is server-side Blazor which doesn't do any of that.