Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> You better show every “buggy” page similar to how the major browsers show them or the new browser will be considered defective.

Used to be true, I doubt that it is anymore.

There are too few (I could find exactly none, to be honest) sites are around these days that are unreadable when rendered strictly according to a newish (say, 2019) HTML/Javascript spec.

The proliferation of front-end frameworks means that almost no site is going out of spec, and because any site that doesn't meet a large portion of the spec is invisible to search engines, having the site be broken when sticking to the various specs is no issue.

In short:

1. With practically all large-traffic sites using a framwork, a browser that strictly sticks to the specs and the specs alone is not at a disadvantage.

2. With important on SEO, a site that is unreadable on a recent spec is not going to be found anyway by the large body of traffic.

Conclusion: a browser that sticks to the spec and the spec alone has a fighting chance.

It's the complexity and edge-cases of an exceptionally large, complicated and self-contradictory spec with thousands of edge-case when different parts of the spec are combined that's the problem.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: