There are several talks about this issue, but I havent found a clear complete explanation of the flaws of the postback model in relation with other models. If you think this is a redundant question, and you are tired of these topics I’ll understand you vote to close it but what I usually read in articles in internet and here it’s the postback model to be mentioned as a flaw of the asp.net webforms model along with others flaws which I understand well (lack of separation of concerns, viewstate, unit testing, etc) but I see no broad, clear and complete explanation of why the postback model in particular is considered bad by many, or I dont seem to completely get it. Someone mentioned pages post to itself, other that some pages using the postbackmodel were slower (is this true?) , and I see detailed explanations of how the postback model and other models run, or theoretical explanations that’s bad because it doesnt follow such philosophy or model, but not a explicity detailed list of what it makes bad in practice. So if you think it would be useful as I think to have such list of items of what it makes it bad in mind when choosing a model for developing, go ahead
Share
The criticism is mostly about two things:
Postback makes your programming paradigm stateful and event-driven. The web is actually stateless, page concept is long since deprecated and the word of today is REST. Postback makes achieving these goals not straightforward.
It makes programmers program as though the web is stateful and keep them in the darkness forever. So Windows programmers continue messing with WebForms like with WinForms. Many ASP.NET programmers with 5-7 years of experience have no idea of how HTTP works.
If you ask why postback is bad as an implementation of an idea to add statefulness to a stateless medium, I have to answer: it isn’t. In fact, it is awesome.
If you ask why postback is bad as a concept, then read above.
Maybe you could clarify for us which point of view of presumed badness interests you.