3 ms·
I'm thankful for that but now they've given us a new even worse monster and we are right back to square one. Remember: IE6 was the best browser for a while, th
by skinkestek 6y ago
I'm thankful for that but now they've given us a new even worse monster and we are right back to square one.
Remember: IE6 was the best browser for a while, the problem was it did things slightly different and people targeted IE instead of the web, exactly as they target Chrome instead of the web today.
- Jonnax 6y agoI think you're misremembering. IE6 was a broken implementation of the standards of the time. And Microsoft decided that web browsing was done and did not update their browser. It was a scheme for vendor lock-in.
- whywhywhywhy 6y agoEnd result is the same. I care a lot about cross browser and the amount of aggravation I have to go to get the developers I work with these days to even look at a site in just safari and chrome, (Firefox is completely ignored) is absurd and the amount of backchat and sarcastic comments of “can’t we just tell them to use chrome” is ridiculous. My career started in the IE 6 era and even then people tested in at least 2 browsers. At most I’ve been lucky to have 1 team member who cares about this stuff. Maybe other companies are better but this is my experience the past 5 years or so.
- boublepop 6y agoJust curious, what is the best way to “target the web” these days? I remember back in the xhtml days that you could validate against standards. But as I understand it these days with google eating up the standards development it seems like html5 is synonomous with chrome.
- skinkestek 6y agoMostly it is really really simple: Do test in Firefox (and Safari). If it works in FF it mostly works everywhere, but Safari has some quirks I think. In fact as long as I test my code in Firefox I haven't been caught with something that didn't work in all browsers any of my customers supported the last 4 or so years. There are a few Chrome-specific things one shpuld
- vanviegen 6y agoYes, they didn't care much for standards. But the larger problem was that they basically stopped implenting new web standards the moment IE was dominant, protecting their Windows monopoly. I don't think many web developers who have really lived through the IE 'glory days' would say the current situation is even nearly as bad.