Your assumption that “using reflection means the code is wrong” seems a bit extreme, at least in .Net. Every time you interact with types, you use reflection. Xml and Json serialization/deserialization uses reflection, and also Entity Framework. If you use mocking in test you are using reflection.

We have an excel export functionality on our sites that uses reflection because we can write 1 function and export any types we want, thanks to reflection.

The only reason that comes to mind to use x264 is to avoid transcoding for older clients. Also Firefox does not support HEVC so it always needa transcoding (at least on Jellyfin)

Sadly some clients (nvidia shield tv) does not support AV1 :( right now I’m encoding some AV1 content I have back to HEVC just because of that.

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.

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.