3 ms·
>> our unique web-platform codebase still faces occasional compatibility problems as web developers focus less on HTML standards and rationally focus on widely
by phkahler 8y ago
>> our unique web-platform codebase still faces occasional compatibility problems as web developers focus less on HTML standards and rationally focus on widely used platforms like Chrome to develop and validate experiences for their customers
IMHO this is not rational on the part of web developers. If they've forgotten the lessons of IE-6 they need to have a refresher and stick to standards. If that means sticking to a subset of the standards that are supported by all browsers then so be it - stop thinking about yourself and your immediate desire (it's not a need after all) and think about the future and your users.
- Timpy 8y agoI think it's becoming clear that chromium is the future. https://xkcd.com/1726/ https://xkcd.com/1726/
- deleted 8y ago[deleted]
- dragonwriter 8y ago> IMHO this is not rational on the part of web developers It's quite rational. > If they've forgotten the lessons of IE-6 they need to have a refresher and stick to standards. I think you have an unreasonable view of what “the lessons of IE-6” for web developers are.
- nirvdrum 8y ago> I think you have an unreasonable view of what “the lessons of IE-6” for web developers are. I agree with the OP. Perhaps you can elaborate on why you think we both have unreasonable views.
- mnd999 8y ago+1
- scrollaway 8y agoSome of the lessons of IE6: - Open source is important. - Web standards are important, especially living standards. - Continuous updates are extremely important. - Bundling browser updates with OS updates is an awful idea. - Plugins are a bad idea, let's not do those anymore. Am I missing any? I know people are afraid of a "browser monopoly" developing around Chrome and I think the fear is very legitimate, but I don't believe this is one of IE6's lessons. There has always been either a monopoly or a duopoly in browsers ever since… well, ever since web browsers were a thing. The web got as far as it did because there was very little fragmentation. In fact, the times where fragmentation was the highest (= when IE versions were legitimate separate browsers and auto-updating wasn't the norm) were the times with the least meaningful progress.
- majewsky 8y agoThe missing lesson: Once a particular rendering engine has beyond 90% market share, it doesn't matter what the standard says. All that matters is what that engine does. We had that with IE6, and again now. There are plenty of Chrome-only sites already.
- phkahler 8y ago>> Once a particular rendering engine has beyond 90% market share, it doesn't matter what the standard says. All that matters is what that engine does. That is exactly the wrong thinking that got people in trouble. The lesson is not to go that route. Every product that has ever existed had an end of life. To tailor your site to the browser of the day at the expense of standards compatibility is short sighted. People like to go for fancy new things and are willing to ignore standards and 2nd place browsers when they don't really have to. Your job is to make a usable site/app, not to show off how you managed to pull of some nifty thing enabled by using fancy proprietary feature X. Stick you your job and check your ego at the door please. You'll be better of down the road. A web site is not a product, it's a way to help sell your product. Unless you're a dot-com company and you're really trying to sell your web site to investors, in which case I don't really care do what you want.
- nirvdrum 8y ago
- sureaboutthis 8y agoIE would ignore published standards and do nothing to move itself into compliance with them or do its own thing without respect to the published standards. Web developers should be writing markup and code based on published standards and not browser platforms. Standards are based on browser implementation so coding to a browser ignores the standard and can make it more difficult for competing browsers to stay in the game if they are unaware such an implementation is coming without previous discussion among their peers. This causes incompatibility issues and its like IE6 all over again.
- piva00 8y agoI think also that the number of front-end developers which experienced the IE6-era is a small ratio of the current total of front-end devs.
- jsight 8y agoAs a web developer who was constantly warning people of the dangers of overreliance on IE6 back in the day, I'm not convinced that the developers were the problem.
- phkahler 8y agoThey failed to say "no". Really, it's a thing. People should try it some time.
- le-mark 8y agoI'm just finishing up a year+ project to make an old IE7 app work on Chrome/Firefox. IE7 is the oldest version that IE11 supports in compatability mode. As it stood, this old app was actually quite impressive. It was a true SPA before SPAs were a thing (2005 or so). It used all the Microsoft specific tech; DHTML, behaviors, htc components, soap/xml, client side xpath/xsl/xslt. Thankfully only a little activex that was easy to replace. Rewriting wasn't an option, but even putting in shims and reorganizing the code was a major effort. Realistically, that's a worst case scenario, and I think it would be a long time before firefox/Chrome diverged to that level, if at all. But the horror, oh the horror....
- criddell 8y ago> stick to standards There are standards, and then there are standards. Ideally, de jure standards would rule the day but in practice de facto standards often win.
- thunderbong 8y agoExactly. If I remember correctly, the older Opera browser was more standards compliant than any other browser at that time. But since developers were primarily coding for IE, Firefox and Safari, each with their own quirks, it just didn't work out for them. I remember doing web development back then and don't recall ever testing for Opera compatibility myself. At the end of the day, you only have do much time. So although my primary browser was Opera, I knew I was in the minority despite all the standards compliance