4 ms·
The problem I have whenever I see arguments along these lines is that nothing is stopping anyone from writing simple HTML using that "subset" if they want to, s
by krapp 7y ago
The problem I have whenever I see arguments along these lines is that nothing is stopping anyone from writing simple HTML using that "subset" if they want to, so a completely separate simpler HTML isn't necessary. If you don't want JS, don't use JS. If you want to vet packages, start a service that vets Node packages. That last part would actually probably be really useful.
- eitland 7y agoAlmost. The idea is to make our browser extremely much faster than the rest of them for rendering such pages. This should hopefully get people to switch to our new browser and force other browsers to start competing.
- krapp 7y agoMost people don't want the modern web replaced with an extremely minimalist version only good for publishing whitepapers, and they wouldn't want to use a browser that enforces such a restriction. Pages with minimalist HTML already render extremely fast in modern browsers, that's not a problem anyone actually has. So why would other browsers even bother to compete with you? Do they bother competing with Lynx?
- eitland 7y agoNo, 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.
- ken 7y agoThat sounds backwards to me. It's corporations which are generating the vast majority of the HTML in the world. Individuals can stop writing JS (and for content-first websites, I have), but that won't stop us from having to see it. Turning off JS entirely will kill a lot of common webpages, so that's not really an option any more. Instead, everybody runs a content blocker, to try to battle with corporations over what dumb junk we're exposed to, or exposed by. Corporations are also writing most of the popular web browsers. This isn't a fair fight.
- zzo38computer 7y agoI do disable scripts. I find that some web pages will still work if you delete or hide an element that covers up everything else (and the script would presumably hide or delete), or unhide an element that is normally hidden (that the script would normally unhide). This doesn't always work, but sometimes it does.
- krapp 7y ago> Individuals can stop writing JS (and for content-first websites, I have), but that won't stop us from having to see it. And that's the rub. None of this is actually about wanting to improve the web with a sane minimalist subset of HTML, or separating "documents" from "apps", it's about wishing the web never left universities, never got mainstream, and never got complicated by modernity or tainted by capitalism. But you can't put that genie back into the bottle and, honestly, I don't think it should be done were it possible. The modern web enables a great deal of creative freedom and cultural expression which simply wouldn't be possible if it were only plain hypertext documents.