4 ms·

What I have been wishing for a while is having well-defined purely document-oriented subset of HTML5 standardized. In practice it probably would mean different

by zokier 7y ago

What I have been wishing for a while is having well-defined purely document-oriented subset of HTML5 standardized. In practice it probably would mean different levels or profiles defined. It could help with many usecases beyond just web, email coming to mind as an example

eitland 7y ago
This might be a brilliant idea, on par with asm.js. Mozilla can implement it like they they did with asm.js, after all it is a subset, not a superset. It will then work in all browsers but (I guess) can be made to work much faster if the browser knows it can ignore the piles of old hacks that full html has to consider. Edit: and like asm.js it might lead to something even better going forward.
jeddy3 7y ago
Brilliant. How can me make this happen?
atq2119 7y ago
The real challenge here is that document and application tend to get mixed up on the web. Looking at even a good old-fashioned blog, there are really three nested things on your screen: the blog post document, the blog post-viewing application, and the browser. Why a blog post-viewing application? In theory you could skip it and just have a plain reader view, but in practice you do want to have navigation and comments, and that's what the application part is for. Many modern systems surface that split in the form of an API: the API is what gives you access to the underlying document. The challenge would be making that solid accessible to the user. For example, could a browser natively have two address bars? One for the document, and one for the application that is used to access the document?
goodusername 7y ago
I have had thoughts around that same idea as well. Could be a start to just define a subset of existing good semantic HTML elements to use for a blog, a news site etc. My dream is to be able to browse a subset of the web, that only uses this kind of document format. Something like docuweb.example.com or whatever :)

by zokier 7y ago

eitland 7y ago

This might be a brilliant idea, on par with asm.js. Mozilla can implement it like they they did with asm.js, after all it is a subset, not a superset. It will then work in all browsers but (I guess) can be made to work much faster if the browser knows it can ignore the piles of old hacks that full html has to consider. Edit: and like asm.js it might lead to something even better going forward.

jeddy3 7y ago

Brilliant. How can me make this happen?

atq2119 7y ago

The real challenge here is that document and application tend to get mixed up on the web. Looking at even a good old-fashioned blog, there are really three nested things on your screen: the blog post document, the blog post-viewing application, and the browser. Why a blog post-viewing application? In theory you could skip it and just have a plain reader view, but in practice you do want to have navigation and comments, and that's what the application part is for. Many modern systems surface that split in the form of an API: the API is what gives you access to the underlying document. The challenge would be making that solid accessible to the user. For example, could a browser natively have two address bars? One for the document, and one for the application that is used to access the document?

goodusername 7y ago

I have had thoughts around that same idea as well. Could be a start to just define a subset of existing good semantic HTML elements to use for a blog, a news site etc. My dream is to be able to browse a subset of the web, that only uses this kind of document format. Something like docuweb.example.com or whatever :)