Problems or flaws in the asp.net postback model

Question

There is some talk about this problem, but I did not find a clear full explanation of the drawbacks of the reverse gear model in relation to other models. If you think this is an unnecessary question, and you are tired of these topics, I will understand that you vote to close it, but what I usually read in articles on the Internet, and here it is a feedback model that is referred to as the drawback of asp.NET webforms along with other flaws that I understand well (lack of separation of problems, viewstate, unit testing, etc.), but I don’t see a wide, clear and complete explanation of why the reverse brochure model in particular is considered bad , or I It seems he did not completely understand. Someone mentioned pages for themselves, others that some pages using postbackmodel were slower (is that true?), And I see detailed explanations of how the reverse model and other models work, or theoretical explanations that are bad because they do not follow such a philosophy or model, but not a detailed list of details about what it does bad in practice. Therefore, if you think this would be useful, because I think you have such a list of items, which is why it does not take into account well when choosing a model for development, go ahead

Answer 1

Criticism basically consists of two things:

• Postback makes your software paradigm persistent and event driven. The web is virtually stateless, the concept of the page is out of date, and today's word is REST. A “return” makes achieving these goals difficult.

• This makes programmers program as if the network were restrained and kept them in the dark forever. Therefore, Windows programmers continue to mess with WebForms, as with WinForms. Many ASP.NET programmers with 5-7 years of experience do not know how HTTP works.

If you ask why postback is bad, how to implement the idea of ​​adding state to an idle tool, I have to answer: it is not. This is actually amazing.

If you ask why postback is bad as a concept, then read above.

Maybe you could clarify for us what point of view of the alleged harm you are interested in.

Answer 2

WebForms is a lie. Its abstraction wrapped in deceit, covered with a false sauce, is presented on a plate full of leakage and sleight of hand. Nothing you do with Webforms has anything to do with the Internet — you let it do the work for you.

Source: Rob Conery