Designing with Web Standard (1)

This book is really good, um. recently, I seem to be a little lazy and read <asp. net server controls and Components> and <Design Pattern explained> did not write any reading notes for a single word, which is a sin. This book can no longer do that, but it is too easy to translate, these masters are easy to understand. where can I extract the wonderful text? It's a mark and I urge myself to take a quick look and read it as soon as possible. Haha.
Part I: Houston, we have a problem
Before you begin
Spiraling costs, diminishing returns
Spaghetti code, deeply nested table layouts, <Font> Tags, and Other redundancies double and triple the bandwidth required for our simplest sites. our visitors pay the price by waiting endlessly for our pages to load. (or they tire of waiting and flee our sites. some wait patiently only to discover that when our site finally loads, It is inaccessible to them .)
Ending the cycle of obsolescence
This is not a book for theorists or purists, but for practical people who need to get work done. it's for creative and Business Continuity sionals who seek sensible advice and a range of proven techniques so that they can modify their skills and thinking and get on with the job of creating great websites that work more visitors and MERs.
Chapter One: 99.9% of websites are obsolete
Lack of browser perfection is no reason to avoid standards. millions of people currently use Internet Explorer 5/5.5 for Windows. from a standards point of view, those browsers are inferior to IE6/Windows, Netscape 6 +, and so on. does that mean if your audience includes ie5/Windows users you shoshould forget about web standards? Does it mean you shoshould tell ie5/Windows users to upgrade or get lost? We think not. Standards-oriented design and development need not and shocould not mean, "designing for the latest browsers only ."