> Web 2.0 is a mistake, because it replaces HTML standards with non-standardized javascript glue code.
This is the most naive statement in your post. HTML and CSS is the problem not JavaScript. The "HTML standards" have failed to provide a standard in any two browsers to do something as simple as a multi-column layout. Meanwhile, JavaScript hasn't changed in ages and works the same in every browser. I'd say you have it backwards.
> It is a sophisticated joke when a simple layout that could have been done by a using a table
The drive for Web 2.0 applications is because users like them. For example, when Yahoo rolled out the new Yahoo! Mail the "non-standardized javascript glue code" got rave reviews from users. Not all users though. I'm sure some longed for full page refreshes, plain HTML and tables - I suppose you'd fall into that group.
Slashdot Mirror
> Web 2.0 is a mistake, because it replaces HTML standards with non-standardized javascript glue code.
o wser-web-20-layouts-part-2-ajax-feed-viewer-20/ with tables?
This is the most naive statement in your post. HTML and CSS is the problem not JavaScript. The "HTML standards" have failed to provide a standard in any two browsers to do something as simple as a multi-column layout. Meanwhile, JavaScript hasn't changed in ages and works the same in every browser. I'd say you have it backwards.
> It is a sophisticated joke when a simple layout that could have been done by a using a table
This one was a close second. Explain to me how you are going to have fixed header/footers/navigation cross-browser with a table? Explain to me how you would create this UI: http://www.jackslocum.com/yui/2006/10/28/cross-br
The drive for Web 2.0 applications is because users like them. For example, when Yahoo rolled out the new Yahoo! Mail the "non-standardized javascript glue code" got rave reviews from users. Not all users though. I'm sure some longed for full page refreshes, plain HTML and tables - I suppose you'd fall into that group.