Comment

Comment on What software stack would you have chosen for Lemmy?

The behaviour you described is very similar to what Blazor is. No frontend framework, and the DOM updates are rendered on the fly. I’m using it a lot and it’s very good.

source

Sort:hotnew top

asyncrosaurus@programming.dev ⁨1⁩ ⁨year⁩ ago
I like Blazor and use it exclusively at my work (usually to build the same type of stuff I’d use a HARP approach in a personal prj).

Blazor is awesome, but really is attractive to backend .Net developers more than anyone else. However, Blazor has a bunch of downsides: Blazor Server is too chatty to build scalable public facing webapps. Blazor WASM has a massive initial payload, which makes it slow and heavy.

Also, it just really falls into being overkill for so much stuff on the web. Half the shit I’m paid to build with Blazor would be faster and cheaper with just some htmx. Most SPAs are attempting to build a sand castle with an excavator.

source
- mordack550@lemmy.world ⁨1⁩ ⁨year⁩ ago
  That’s my case, i’m a backend developer, more specialized in databases than websites, so i choose blazor because it was easy for me to become proficient fast and build nice and fast apps.
  
  Also i usually build Enterprise apps, not public facing ones, so my target is still good for blazor. I know there are methods to scale better with blazor server (like using signalr on a separate service, outside the webapp).
  
  Also we use DevExpress components, so basically all UI controls are done for me, so my dev time is even lower.
  
  I’ll look at htmx, i’m curious at the tecnical differences and why it may be lighter than blazor.
  
  source
- RonSijm@programming.dev ⁨1⁩ ⁨year⁩ ago
  
  […] Blazor WASM has a massive initial payload, which makes it slow and heavy.
  
  Blazor WASM doesn’t need to have a massive initial payload, that’s only if you’re making your projects too big, and aren’t really structuring them correctly. To be fair, Microsoft hasn’t really done anything to make this easier, or address this
  
  (Shameless self promotion) - I however, have fixed that: github.com/RonSijm/RonSijm.Blazyload Your “landing page” should basically ideally be pretty much the only thing that’s initially loaded, so that the initial load is fast. Once that is done, you can quietly lazy load the rest of the dlls you need
  
  source