4 ms·
I take a similar approach for 9/10 of the enterprise web apps I build, but use ASP.NET Core MVC instead of PHP, and I also favour SASS. Point is that SSR (Serv
by GordonS 7y ago
I take a similar approach for 9/10 of the enterprise web apps I build, but use ASP.NET Core MVC instead of PHP, and I also favour SASS.
Point is that SSR (Server-Side Rendering), with a sprinkling of simple JavaScript and XHR calls as required, is enough for almost everything I do, and it means build are really simple. Doubly so with a strongly typed language like C#.
I've worked on Angular and Vue projects, and the complexity level was (subjectively) much higher, despite these particular web apps not requiring any real level of client-side functionality. I find JS tests to be much more complex and brittle than C# ones too. Honestly, I hated it! Now, some of this was undoubtedly because I'm more comfortable with what I know, but certainly not all of it.
- pixelrevision 7y agoPeople vastly underestimate how complex client side code can get and how much automatic functionality browsers hand you. Whereas a nice web framework has users, permissions, session management, templating, validations and forms all set up for you with battle tested out of the box behaviors. A frontend framework is great if you are a company that really needs to slim down bandwidth and can hire expensive devs to maintain it. But for a simple no nonsense business application it’ll just slow you down and will gravitate towards being a mess.
- elboru 7y agoHave you tried Razor Pages? I used it in my last project and I loved it, it was a lot simpler and subjectively more fun than using regular MVC.
- GordonS 7y agoI haven't tried it, but have read uo a bit and seen some examples. TBH, I'm not all that keen, possibly because it reminds me of the bad old days of webforms with code-behind files. Maybe I should try it in anger before I judge it though :)
- nsfwfavorites 7y agoDetermined gripping agama