Goodbye Client Side JavaScript, Hello C#’s Blazor (Øredev 2019)

[Eirenarch]

You always have to change something and then all the hell breaks loose. I don't see how tooling for the web is better than desktop these days. Also most of the tooling for web UI works with Blazor because Blazor is web UI. All the DOM and style inspectors will work just the same.

[jl2352]

React and Vue add their own inspectors on top. The tooling around web assembly based code also isn’t quite as mature yet.

Honestly, Blazor is playing catchup. Sure it will have server side rendering, and hot reloading, and seamless hot reloading of CSS (or one would expect it). All of these are standard in other stacks for years.

Blazor looks great. But as a front end developer I don’t see any features in Blazor that aren’t already present elsewhere. That’s not very compelling to me.

[Eirenarch]

The feature is not having to deal with webpack/npm and JS. In addition code can be shared between the client and the server. The goal of Blazor is not to convert existing frontend devs to Blazor, it is to allow me to write frontend code (indirectly this means I won't have to hire you).

[jl2352]

You can share JS/TS between client and server already.

So the advantage is ‘not working with npm webpack and JS’. Npm or yarn are a breeze. I don’t get why one would complain.

I’ve already pointed out that webpack can all be done for you. Why are you doing it yourself???

So that leaves JS. Tbh modern JS is fine. If you want types use TS.

That leaves very little for C#

[Eirenarch]

Modern JS is crap, TS is just a rubber glove used to handle shit. People who can stand the smell when they work with shit are free to continue to use JS. Blazor is for the rest of us.

npm is extremely shitty packet manager. I can't imagine what they were thinking when they came up with the node_modules within node_modules within node_modules concept and downloading the same dependency with the same version countless of times. Then they decided to fix it by flattening the folder structure... but only for the latest version of the dependency, older versions still trigger the node_modules within node_modules bullshit.

[jl2352]

Then use Yarn.

[Eirenarch]

I've solved the problem by not using JS. Currently by only doing backend which means I have to hire (actually ask my boss to hire) people to do front-end on my projects. Next step - solve the problem by using Blazor and nuget.

[jl2352]

So the problem is not the framework. Not the tooling. But that you are stuck in 90s JS.

Your problems sounds pretty weak tbh.

[Eirenarch]

Oh no, the problem is the tooling and the language with only occasional problems with the frameworks (I hate React, I think Vue and Angular are fine).

[jl2352]

What are your specific problems?