Earlier quoted context omitted.
Perhaps you are being a bit too strong here. I might hold an uncommon contrarian view for news.yc but, here goes nothing: "It teaches its victims to use the excreable "viewstate" and POST when they mean to GET and pass volumes of unnecessary and poorly-encoded data back and forth between the server and client." You are right here to the extent that "viewstate" is the default way of managing state, scalably, in ASP.NE…
Thanks - that was a very nice and thorough response. And I quite agree with much of what you said. You don't have to use "viewstate" and flow layout is the sensible thing to do. But in actual practice .Net projects often do use viewstate and POST even when GET is appropriate and .Net projects frequently use absolute positioning even when flow is clearly approprate. As I said, it IS possible to do good web projects wi…
For some reason I thought you were talking about "Reports" and "Reporting" in general, as offered by the Report Viewer Controls in ASP.NET (using rdlc / rdl).
I have used CSS in the past to allow users to print pages (as they see it on the page) and it has worked well for me. Although Report Viewer Controls in ASP.NET have their own magical hold on the business users (Probably because they are made to look and feel similar to other Reporting Packages, which Business Users are comfortable with). So, I still think thats a good way to go, if that is your audience. :)
But, I do understand what you are saying and agree that there is the possibility of people using this technology where it shouldnt be used.