loading...

re: How Blazor Is Going to Change Web Development VIEW POST

TOP OF THREAD FULL DISCUSSION
re: I replied to a comment of yours on another article but since you probably haven't seen it, I'll reproduce it here. Your original comment: "Growing...
 

There's no doubt: the power of C# outshines all Javascript stacks in every way. (For now).

Will Blazor make it? Perhaps but there are no jobs.

There's too many questions like: Will it be the wave of the future? Is it a market disrupter? Will its eco system trump NPM and Javascript? Will MSFT start supporting thier adopters? Are they now all of the sudden loyal?

Will they rewrite VS Code in C# WASM? Never, Electron and Typescript work beautifully for millions of developers daily.

Chrome, the browser that won, will remain a Javascrpt friendly stack.

Many large corporate websites are aleady running Isomorphic Javascript stacks? Need more power? Spin up another server.

Node is making progress on CPU agnostic design. Compiled Javascript in WASM will happen.

Both Java and Javascript are more popular than C# in 5th or 6th place.

Finally, most of people who only grew up on Javascript dislike MSFT passionately. Their only view of MSFT was the inane Internet explorer and Edge. MSFT caused them as much pain as their desktop crowd.

Of course there are not many jobs YET, server-side Blazor launched with .NET Core 3.0 only this September, while client-side Blazor is still in preview and will launch in May 2020, if all goes according to plan.

It is possible to host Blazor on Electron for desktop apps:
github.com/aspnet/AspLabs/tree/mas...
However, they haven't stopped there:
blog.stevensanderson.com/2019/11/0...
It does away with Chromium and Node for significant download size and memory footprint savings.

The newer IEs were arguably much better than older ones, while Edge was better still and now there is Chromium based Edge, so nothing left to complain about.

One of the main selling points of Node was a relative speed advantage: no longer true. Another was enabling same language development across front- and backend while others didn't: also, no longer true.

Hell, Python is most popular now and it's a slow, niche language, only ideal for ML/AI. Already for webapps there are many alternatives that are far better and for game development you can forget about it.

Oh yes, some people hate and will hate MSFT no matter what, and that has nothing to do with the quality of .NET Core/Blazor.

code of conduct - report abuse