4 ms·
Downvotes totally undeserved. The notion that you have to use a specific browser- even if it's "a modern browser"- should have died with IE 6. Progressive enhan
by ajacksified 15y ago
Downvotes totally undeserved. The notion that you have to use a specific browser- even if it's "a modern browser"- should have died with IE 6. Progressive enhancement of web applications is not hard, and is only overlooked because of ignorance or laziness.
"use chrome" sounds an awful lot like "site only available in IE 6". That's why we're in this mess.
- melling 15y agoI just went through this with someone else. It's completely different. IE6 specific was not any sort of standard. There really isn't any need to nurse people along until they feel the need to upgrade. "Progressive enhancement" does cost money and take time, which could be better spent on people who upgrade to a modern browser. This is all obvious, right? You can also use Firefox as far back as 3.6, an "ancient" browser, if you'd like.
- ajacksified 15y agoIt's not different. It's not different at all. It isn't about standards, it isn't about IE6 or FireFox or Chrome. It's about providing a baseline of functionality and building up features. It doesn't cost any more money or take any more time than it does to build top-down - and in fact, in the long run, there's a quantifiable cost savings in maintenance of an application built with a solid foundation. It's not more work, it's just working differently. You'd plan and build your back end to scale, to be maintainable, to be testable; why not the front end?