2 ms·
Reminds me of the principles behind the original asp.net, all the way back in 2000. At the time there were no websockets, so it was done with constant post-back
by toyg 8y ago
Reminds me of the principles behind the original asp.net, all the way back in 2000. At the time there were no websockets, so it was done with constant post-back, but the principle was fundamentally the same: develop like it were a local app, the framework will take care of the rest. Let’s just say it didn’t get very popular in my neck of the woods. I’ve since moved on to other things so I don’t know what modern asp.net does, but I bet you can still code this way if you really want.
(Not that you should, imho: trying to bypass the fundamental architecture of the web is typically a way to end up in debugging hell.)
- sixdimensional 8y agoFirst, there was ASP, which was a lot like PHP, ColdFusion or Perl/CGI - mixing inline back-end code and HTML/JS/CSS/etc - but of course executing all back-end code on the server. ASP.NET WebForms came along and is still supported, and tried to make developing web applications similar to developing desktop applications in WinForms. I did that, it worked.. it was clunky at times (but it worked). Of course, mostly this was all server-side with just HTML/JS/CSS interacting. A long time ago the dominant model became ASP.NET MVC which is a typical server-side MVC architecture. Recently, Microsoft offered a new "old" paradigm through Razor Pages which are a lot like old ASP was. If you look at things like React (or the view layer in Angular, etc.), it turns out that the web component / control model used in WebForms (server-side) is quite similar to the client side model used in React. The main difference of course being, one running client-side primarily (React) and the other server-side (WebForms). It gets even more interesting as a comparison when you talk about server-side React view rendering.
- toyg 8y agoYep, I was thinking of the original WebForms.