Recently WHATWG editor Ian Hixie floated the idea of dropping HTML/CSS in favor of WASM & some of the lower-level APIs. Stating that he's given up on the HTML/CSS vision.
I haven't given up on that vision, but you know what? If this move gets clientside webapps out of my hair, I'm in favor of it being pursued!
I've stated before that I think the document web & app web should diverge!
@alcinnz can we drop the illusion of the "web app" vision and adopt a stack modeled after mobile app sandboxing?
@loke @lunch @alcinnz @Azure Themeing is one of the biggest things I feel is missing from the web. I love being able to customize my desktop experience.
In @agregore I've been encouraging apps to import a CSS file that can be customized by users in order to apply some default styling to an app. I still need to make it easier to make new themes, but at least it gives web users a bit more power than they have now.
@alcinnz @loke @lunch @Azure Right?! There's a whole module in CSS for exposing this stuff to users. https://developer.mozilla.org/en-US/docs/Web/CSS/system-color It's defined right there but none of the browsers bother pulling your theme from your OS.
@mauve @loke @lunch @Azure @agregore This btw was always part of the CSS vision for the web, just it never paned out due to the feature being too hidden & limited.
And it's a feature I like focusing on! Maybe after growing up with CSS webdevs would be more receptive, there's signs...