Blazor: a new web ui framework

In one of my favorite movies there is a quote that goes:

“Roads? Where we’re going we don’t need roads…” 

And it all looks the same; cause every way you turn, there is Javascript everywhere. If you use any front-end framework, there is always Javascript. And I have nothing against it, but all the years of ANSI C, C++, JAVA and .NET C# (or VB) lead us to Javascript? I don’t want to believe so…

js

There are different things that strong typed languages handled in a very elegant way, besides the fact that people who has been developing on .NET since it’s 2003 version, might want to leverage all of that into the new era. And it is difficult to do so, rather than creating a web api service here and there.

However, there is a new thing called Blazor. But… what is it exactly? Microsoft has built an experimental release of something called Blazor that builds web projects in WebAssembly so you can write all your code in C#. And WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine. Wasm is designed as a portable target for compilation of high-level languages like C/C++/Rust, enabling deployment on the web for client and server applications.

If you already use .NET, this completes the picture: you’ll be able to use your skills for browser-based development in addition to existing scenarios for server and cloud-based services, native mobile/desktop apps, and games. Voila! That simple!

Here’s a view of its architecture:

Blazor is based on existing web technologies like HTML and CSS, but you use C# and Razor syntax instead of JavaScript to build composable web UI. Note that it is not a way of deploying existing UWP or Xamarin mobile apps in the browser. To see what this looks like in action, check out Steve Sanderson’s prototype demo at NDC Oslo last year or his prototype demo for the ASP.NET Community Standup. You can also try out a simple live Blazor app running as a static site.

So going back to the original quote, why does it ring a bell when we are talking about this again? Easy, even when ASP.NET Forms aspx was in, and there were some not-so-friendly Frankenstein solutions with Castle Windsor, MVP in a weird way and what not, Microsoft always reinvented themselves to be up to date and launched ASP.MVC at that time to “compete”.

So is this the future? We don’t know… what we know for sure is that where we’re going, we don’t need roads…

The following two tabs change content below.
I am Diego Gravisaco, I live and work in US. I am originally from Argentina, but I worked and lived in several places as a .Net Tech Leader and Software Architect including Paris, France; Tampa, Florida and other places. I have been working as a Software Architect for quite some time now implementing Service-Oriented Applications and distributed systems with Microsoft Technologies using Agile practices. You can take a look at my linked in page: uy.linkedin.com/in/diegogravisaco

Latest posts by Diego Gravisaco (see all)

Deja un comentario

Tu dirección de correo electrónico no será publicada. Los campos obligatorios están marcados con *