4 ms·
No, it doesn't need to be minimalist. Styling is totally OK. And the browser could even be Firefox, just with a separate rendering path if it detects the page
by eitland 7y ago
No, it doesn't need to be minimalist.
Styling is totally OK. And the browser could even be Firefox, just with a separate rendering path if it detects the page is html5core or whatever.
Old pages works just as before. New, html5core compliant pages loads blazingly fast and displays just as nice though.
- krapp 7y agoBut as far as I can tell, 'html5core' is just a subset of HTML meant for static documents, meaning it's just HTML. There's no reason for that to have its own separate rendering path, or even to be its own thing. The process of validating it as 'html5core' would probably take more time than just rendering it as is.
- eitland 7y agoI think you misunderstand. Html and a limited subset of css is OK. I'd try to remove unused constructs but more importantly for the speed: as much as possible of what stands in the way for efficient rendering. In the second model there's even room for limited Javascript, think autocomplete and reloading of parts of a page etc, the only thing is it will work more like components with parameters instead of a Turing complete language. It will definitely not take more time to decide: you add a marker to the start of the document. The browser then sends it the fast path.