Introducing this new concept immediately brings questions, and rightfully so.
One of the benefits of opening up the web to .NET in particular is that we now have alternatives to npm and WebPack. As a long time .NET developer, I’m greeting NuGet (package manager) and MSBuild with excitement. For me, these technologies are less problematic, more familiar, and far more productive. While nothing is ever perfect, my relationship with NuGet and MSBuild has been mostly positive.
I feel that WebAssembly shares a similar goal. In fact, that goal is stated on the official WebAssembly documentation.
Is WebAssembly something that interests you? Do you plan on testing out Blazor? Or are you a developer from a background like Ruby or Python that would like to use WebAssembly in your pipeline? Share you thoughts in the comments below.
Subscribe to be the first to get our expert-written articles and tutorials for developers!