| > I think supporting everything but javascript for the "document browser" would automatically enable a ton of websites and make it easier for creators and consumers to use the tools and languages they already understand. There are some merits for that, but I think that is both excessive and deficient at the same time. > https://erock.lists.sh/browser-monopoly I think that these are valid points, which I have some comments relating to. > Support HTML 5, CSS 3, HTTP, TLS You can add other file formats and protocols too, such as Gemini, Gopher, and possibly Markdown too. > Maybe remove website specific styling altogether and instead design a consistent design that optimizes navigation and readability. That is what I think too; even the HTML with no CSS, will be OK. Perhaps let the end user to specify colours, fonts, etc. > Allowing the user to query for information and have that data displayed without full page reloads (AJAX) For data-oriented stuff, you could also have such things like <a rel="data">, you can just get the data and use your own software to display it. > I want a minimal, modern set of browsing tools where I don't have to make any sacrifices between usability and compliance with the standards. Yes, I think so, too. Splitting all of the components separately is one start, I suppose (although it is not good enough by itself) (a C program can then be written to tie them together, and this can be changed as needed, including to add/remove components) (this is like reversing core and extensions the other way, so that e.g. HTML and HTTP are now extensions instead of core). However, half of the standards are I don't want quite compliance and should deliberately implement them in a better way than what they say. |