A JS coder's view on Blazor

A JS coder's view on Blazor

Jan 22, 2020ยท

0 min read

Play this article

There's certainly a hype around every new technology which promises a lot to the target users. Blazor is one of them. For C# devs who are too lazy to learn JavaScript, Blazor is certainly a saviour.

After going through the installation and setting up my first Blazor app, I certainly have a few thoughts about Blazor.

My thoughts on Blazor

  1. Blazor may be fast when fully loaded in the browser, but by default, it takes time to load. Comparing this to the fast load times of apps built with React or Gatsby, it is certain that Blazor goes against the "fast load times" philosophy.

  2. Blazor uses C#. This means for web developers who want to learn C# for whatever reason, Blazor serves as a platform for them to use the language. (I'm one of them).

  3. The fact that C# is used means you don't have to face the downsides of the flexibility of JavaScript. You get to use a robust language.

  4. No need for node_modules ๐Ÿ˜Š. Truthfully, I hate the fact that for any modern JavaScript app, you need to download a whole directory of node modules which is usually > 60 MB. This may not be a problem in environments with cheap WiFi and low latency, but it's a serious pain in environments with expensive data and slow internet. Some of us end up copying old projects, cleaning them up and adding new files.

So, by far, I'm glad I jumped into Blazor at the early stages of its development and acceptance. I believe the framework will keep getting developed. I also love the bonus it offers. I get to learn C#! I can finally develop games using Unity and not feel totally lost.

If you believe you'll blend well with Blazor, I'd say you give it a try. It won't hurt much. And you get to learn C# if you don't already know C#. To get started with Blazor, check out the docs.