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.
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?
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.