this post was submitted on 11 Apr 2026
35 points (97.3% liked)

Linux

13228 readers
68 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] certified_expert@lemmy.world 0 points 1 day ago (1 children)

I am not web or ui dev. But I think using html/css as frontend seems kind of reasonable, no? Expressive enough, simple enough, well known

What is the problem? Too heavy to interpret?

[โ€“] OwOarchist@pawb.social 4 points 1 day ago

Needing to run a full-fledged browser in the background in order to display your html/css frontend adds a lot more performance cost than necessary, making the app eat up far more RAM and CPU than necessary. It probably also introduces a lot more security vulnerability concerns that an otherwise simple app shouldn't have to worry about. And then there's the dependency chain you're introducing -- now your app needs to be updated every time the underlying browser gets an important update ... and maybe needs to be tweaked/rewritten to accommodate that browser update if it changes the way the browser interacts with your app frontend.

There are plenty of other GUI frontend frameworks that are also expressive, simple, and well-known, without all of these potential problems associated with them.