News for hackers. Stuff that matters.

A comment on Future CSS: State Container Queries. Parent comment

Re:Future CSS: State Container Queries by codethief on Thursday June 29, 2023 @03:18AM (#36517406)
I've been thinking about this lately: Writing a rendering engine for WASM or something, which then draws to a canvas.

The rendering engine can then be shipped along with the actual UI.

Sure, the rendering engine will take some time to load. However, compiling styling etc. to WebGL instructions at build time might also speed things up considerably.

(The actual reason, however, I'd be interested in this is not performance but improving upon the developer experience and replacing CSS with something better.)

[ Parent | on HN ]
Re:Future CSS: State Container Queries by ly3xqhl8g9 on Thursday June 29, 2023 @03:30AM (#36517498)
To keep in mind, à la longue, the best CSS is probably no CSS. Does a user really need all these buttons and dropdowns, modals and scrollable containers, or do they need only an input and a container rendering a few paragraphs, an image, a video/audio, possibly a 3D model.

I see no problem if instead of using all these web sites/applications with such a plethora of visual and experience spam, I just have a single input box connected to an agent through which I interact with them all, letting the APIs settle in the background.

[ Parent | on HN ]