@Shamar It's going quite well!

I'm now working on an auditory web browser, which is a surprisingly elegant design. Both it and Odysseus are nearing completion on their basic featuresets!

Then I'll tackle a smart TV browser, possibly preceded by a print one!

I've decided to target unusual devices to better show the power of HTML/CSS, give myself a better sense of progress, & to try bending IoT hype to combat JS hype.

@Shamar I've just read those links, very interesting!

On the second one ("Why Forking HTML...") I'd state:

1) I totally understand where he's coming, document layout is complicated (more complicated than apps infact) & it's disrespectful to various cultures to pretend otherwise.
2) I'm implementing a subset to make sure I know what I'm talking about.
3) Voice assistants/screenreaders, smart TVs, etc could provide incentive... Without this subset they provide a poor UX.



4) I find that rendering forms inline on a page provides a poor UX on various platforms/devices, leads to uglier browser-engine code, & tempts webdevs to break OS consistency. It's easier when that's moved to a seperate codepath.
5) Removing JavaScript, it's APIs, the over-engineered OOP "Document Object Model", & constraining page updates is a massive simplification. That easily ammounts to over half of a modern browser engine.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves. A STEM-oriented instance.

No hate, No censorship. Be kind, be respectful

We federate with all servers: we don't block any servers.