5 ms·
> you owe it to yourself and your team to use a proper JS framework and toolset. In 2023 JS is no longer necessary, for instance, Blazor also works fine, and w
by sebazzz 3y ago
> you owe it to yourself and your team to use a proper JS framework and toolset.
In 2023 JS is no longer necessary, for instance, Blazor also works fine, and works great for small teams building just LOB apps.
- aloha2436 3y agoBlazor Server and WASM both have issues that make them non-starters for me, namely latency quickly gets out of hand for the former and the latter is far too heavy. The (unfortunate?) reality is that Javascript is unavoidable if you want good bundle sizes and client-side interactivity. I find HTMX is a better alternative if I'm trying to write as little JS as possible, I find it smooths over the latency issue better and just lets me write normal web app code that feels like a SPA to use.
- chrisco255 3y agoHi, do you have an open source repo of something you've built in Blazor? Would love to check it out. While it sounds interesting, there are still numerous limitations to wasm. There's no garbage collection, I'm curious how large Blazor apps are at scale on larger code bases, I'm also curious how well that works with either a PHP or Ruby stack, for example, and how easy you find it to integrate with other frameworks outside of the Microsoft stack?