ASP.net & designing with web standards (Zeldman aloud #2)
Still in overture mode I guess...
Spiralling Costs, Diminishing Returns
- Some coding tricks (such as using nested tables for layout or font tags bloat our pages.
- This swelling causes users to wait longer for our sites to download and increases our expenditure in hosting.
- Having to code different versions of our site for different browsers and devices increases developing costs n-fold.
There's a very interesting catch here for us ASP.net people (actually this very same point could also be made of every other server-side technology, such as PHP or ColdFusion): a lot of this code excess is inadvertently created by some of the (seemingly simple) controls we use in our code.
An innocent ASP.net tag such as a grid can eventually result in a plethora of tables scattered all around. And yet, the extra price we're paying for all those tags can very easily go unnoticed. But I like ASP.net grids!. I'm not recommending solutions (yet), just pointing out risks and problems. Patience, dear reader, is quite singular a virtue.
Alan - yet another Aggiorno evangelist