News for hackers. Stuff that matters.
Re:MVC frameworks aren't dinosaurs but sharks by jolux on Monday May 09, 2022 @07:08PM (#31321079)
WebForms is an unrepresentative example because it needs to carry all the view state between the front end and backend and was enormously complicated under the hood to make the programming model easier. Nothing else works like that, the state is stored in session storage in memory on the server, and the client just sends a cookie containing the key for its session.
Re:MVC frameworks aren't dinosaurs but sharks by jiggawatts on Tuesday May 10, 2022 @01:00AM (#31323622)
To add to this: Microsoft recognized that third-party control developers were dumping too much info into the ViewState bag, and this was largely fixed in later versions.

It's also possible to store ViewState "on the server side" instead of on the client side. So instead of sending megabytes up and down with every request, the client just gets a unique identifier. The downside is increased memory usage, but that's often better, especially for internal enterprise apps.

Re:MVC frameworks aren't dinosaurs but sharks by jolux on Tuesday May 10, 2022 @08:24AM (#31326216)
Yeah, ironically the way people try to do stateless backends and heavy frontends with JWT is closer to the ViewState mess than normal MVC apps.