IssueRaiser

I should clarify, I think they should be strictly following web standards, and by doing so, they help to force those sites not following ...

I should clarify, I think they should be strictly following web standards, and by doing so, they help to force those sites not following standards to update their code, or die. I don't want my browser using extra resources, and having extra features and menus to improve compatibility with someone's sloppy, hacked together website from the 90s. I'd rather that site appear broken because it's not following standards, and by doing so, it's encouraged to update, or be replaced by someone else. I believe this would allow for a smaller browser footprint, and we'd see better coded websites in the long run, instead of carrying them through. For example, we get a new IE browser, that follows standards to the T. If your site doesn't work in IE, it's not because "it's IE, use a real browser", it's because you didn't code your site properly. In the video they talk about how they would previously look at the top 10k websites and ensure compatibility, and now they're looking at millions and billions. They shouldn't look at anything. If Reddit doesn't work in the new version of IE, because they're not following standards, then so be it. Don't look at methods of relaxing those standards and bending the rules to get Reddit working. Leave it broken, and let the users apply pressure to Reddit because the site isn't working in IE. As I said above, they can't laugh off IE anymore, because it's not some dumb, outdated browser. Instead, it's following standards, so Reddit is broken, not IE. It would be the gold standard... in standards. You check to make sure your site works in IE, because if it does, then you coded it right. If your site displays fine in Firefox and Chrome, you don't really know if it's coded properly, or if they just held your hand to make it display correctly.

Posted by Throwaway90283 on Feb 27, 2015, 2:50 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.7,500 issues0 comments

reliability (Other)

I should clarify, I think they should be strictly following web standards, and by doing so, they help to force those sites not following ...

Throwaway90283Feb 27, 2015, 2:50 AM

I should clarify, I think they should be strictly following web standards, and by doing so, they help to force those sites not following standards to update their code, or die. I don't want my browser using extra resources, and having extra features and menus to improve compatibility with someone's sloppy, hacked together website from the 90s. I'd rather that site appear broken because it's not following standards, and by doing so, it's encouraged to update, or be replaced by someone else. I believe this would allow for a smaller browser footprint, and we'd see better coded websites in the long run, instead of carrying them through. For example, we get a new IE browser, that follows standards to the T. If your site doesn't work in IE, it's not because "it's IE, use a real browser", it's because you didn't code your site properly. In the video they talk about how they would previously look at the top 10k websites and ensure compatibility, and now they're looking at millions and billions. They shouldn't look at anything. If Reddit doesn't work in the new version of IE, because they're not following standards, then so be it. Don't look at methods of relaxing those standards and bending the rules to get Reddit working. Leave it broken, and let the users apply pressure to Reddit because the site isn't working in IE. As I said above, they can't laugh off IE anymore, because it's not some dumb, outdated browser. Instead, it's following standards, so Reddit is broken, not IE. It would be the gold standard... in standards. You check to make sure your site works in IE, because if it does, then you coded it right. If your site displays fine in Firefox and Chrome, you don't really know if it's coded properly, or if they just held your hand to make it display correctly.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue