3 ms·

Can we flip this for a bit? What would be of web as an application development if swappable themes was a requirement? - Wouldn't it be easier to have WebCompon

Can we flip this for a bit? What would be of web as an application development if swappable themes was a requirement? - Wouldn't it be easier to have WebComponents as an actual useful technology? - Wouldn't it be easier for browser engine developers to have an "strict mode" of sorts that could run optimized code for actual apps? - Wouldn't it be easier to develop client-side code for other languages that would deal with nothing but business logic, instead of forcing us to come with something like WASM? - Couldn't web clients perhaps come bundles with a set of these web components and styling themes, and wouldn't perhaps the browser be efficient enough to allow us to ditch mobile-clients? - By not having to support multiple clients and platforms, wouldn't we be able to avoid re-inventing JSON as a poor version of X(HT)ML? - Wouldn't the web be a lot more programmable and mash-able and lead to a lot of these server-side functionality to not be needed in the first place?

jmchuster 5y ago
Hmm, if we were to really support user-swappable themes, one of the first major problems that comes to mind, is how do you split what the user should change vs what they shouldnt. Where do you draw the line, and then how do you make sure the user doesn't break things, only styling, and styling in a manner that leaves the interface still fully workable, with the worst offense being it might be "ugly".
- rglullis 5y ago
  Honestly, I am not even thinking about user-styling, only about setting some stricter separation between styling and structure for the browser. My dream world would be one, like in Zen Garden, be based on two principles: - the designer has no way to alter the document body structure, only the header for CSS file declarations. - Any kind of feature/effect that the designer could only achieve by changing the structure should be considered a P0 bug by the CSS engine developers.

jmchuster 5y ago

Hmm, if we were to really support user-swappable themes, one of the first major problems that comes to mind, is how do you split what the user should change vs what they shouldnt. Where do you draw the line, and then how do you make sure the user doesn't break things, only styling, and styling in a manner that leaves the interface still fully workable, with the worst offense being it might be "ugly".

rglullis 5y ago
Honestly, I am not even thinking about user-styling, only about setting some stricter separation between styling and structure for the browser. My dream world would be one, like in Zen Garden, be based on two principles: - the designer has no way to alter the document body structure, only the header for CSS file declarations. - Any kind of feature/effect that the designer could only achieve by changing the structure should be considered a P0 bug by the CSS engine developers.