Did WASM solve a problem that now isn’t one?
The problem was JavaScript. .Net devs hate it. So did I. Blazor held the promise of eliminating it by letting you build your interactivity with C#.
Somewhere along the way, while WASM devs sweated though all the tradeoffs of slow initial load and lack of SEO, Claude came along and offered to build our JS for us, and it did it extremely well.
So when we a step back, isn’t it clear that Blazor is the best composition tool for the server, and JavaScript is the best and defacto standard language for client-side interactions?
All I’m saying is Claude has allowed me to lean into JS instead of dreading it. And the larger lesson, use the right tech for the job.
In our world, Blazor has become the new MVC. Tailwind is the new Bootstrap. DaisyUI sprinkled in lends a helping hand with modals and other widgets, but at OUR discretion.
And JavaScript is the new JavaScript. If you are stubbornly SSR like me, that won’t change. But libs like BlazorJSComponents help componentize it, and Claude is brilliant at building it where needed.
Embracing vanilla JS is like embracing JQuery in 2008. It’s a bit kinder and gentler now that we have Claude. Want partials/fragments? Grab HTMX, or build your fetcher/swapper in a couple hours.