4 ms·

Just stick with the classic frameworks. Razor works great as does MVC WebAPI

• pier25 10mo ago
  I tried Razor. It's mature, has tons of features, and it's very fast. But it only really solves rendering HTML. You will still need to integrate Vite somehow to use modern CSS, TS, etc. And if you do that, why even use Razor to begin with? Also, hot reload is garbage. C# will never get close in speed or features to something like Vite.
  • shortrounddev2 10mo ago
    If youre intent on writing everything on the frontend in javascript then you can just have a frontend app and use webapi MVC on the backend. Personally, in my personal projects, I find I iterate faster if I dont't write any javascript. Every page is just static HTML and any interaction is done via CSS (which you can do perfectly well in razor pages) or html forms. Managing page state is a huge time sink and IMO not worth it, but it's what pays the bills lol
    • pier25 10mo ago
      > If youre intent on writing everything on the frontend in javascript then you can just have a frontend app and use webapi MVC on the backend. Yes, I'm aware. I've been doing web dev since the 90s. > my personal projects, I find I iterate faster if I dont't write any javascript It's expected you will iterate faster if you have less features, no?