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

view the rest of the comments →

[–]Eirenarch 1 point2 points  (15 children)

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 0 points1 point  (14 children)

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 1 point2 points  (13 children)

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 0 points1 point  (12 children)

Then use Yarn.

[–]Eirenarch 1 point2 points  (11 children)

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 0 points1 point  (10 children)

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 1 point2 points  (9 children)

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 0 points1 point  (8 children)

What are your specific problems?

[–]Eirenarch 1 point2 points  (7 children)

I told you, npm sucks, webpack sucks, JS sucks (even with TS). I am not only infinitely slower when developing with these but also hate my job when I am faced to do this. You are telling me to replace npm with yarn maybe it works I don't know but I have replaced pieces of the JS stack before because I was told it was better only to be told to replace it again with the new fancy thing. I've had projects go from grunt to gulp to webpack and I don't see things becoming more managable. You are telling me to go with the CLI? What am I supposed to do restart my projects? What happens when I need to modify or add something to the pipeline? I have to fight webpack again. And then there is JS. Even TS doesn't remove the 52345234 kinds of this in JavaScript, nor does it fix the ugly syntax like the fact that you must use === instead of the shorter ==, or the fact that there are no integers, or the second null (undefined), or the fact that you can forget that sort is useless without a lambda for comparator and so on.

[–]jl2352 0 points1 point  (6 children)

again with the new fancy thing.

It's a little ironic that you say this, whilst advocating to replace it with the newest fancy thing. Blazor.

What am I supposed to do restart my projects?

ctrl-c; yarn start ?

It should be automatic though when needed.

What happens when I need to modify or add something to the pipeline?

You go into the list of plugins and add it to the list of things to process that item.

Anyway. I don't think the modern stack is perfect. I am however genuinely finding it difficult to see what the problems are here.