title: problems or flaws of the asp.net postback model
body: <p>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 </p>