Sure you can build rich stuff, but doing it is clunky, not standardized
and
unproductive. The average developer struggles to get his head around
all of
it because there's a lot to learn and too many choices to make.

Most x-browser stuff is handled by toolkits (prototype, jQuery, etc.)
these days that you don't need to worry about it. We produce a SaaS app
that is supported on IE, FF, Opera and Safari, on Windows, Linux and Mac
and we don't think about x-browser much at all. And we handle ajax,
drag/drop, dynamic DOM, etc. Is there x-browser stuff deep in the
toolkits? Sure. Do we care? Nope.

-Walden


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.