It’s not CEF that does most of the impact. It’s the contents web devs make it load and process. And web devs generally not being very competent in optimizing is just a sad reality.
web Devs aren’t ignorant to optimizing but the kind of interfaces used in web are very different to that of desktop. Cross platform technologies can work, but anything built on top of web engines is going to be a little dogshit on native platforms.
Web tech was designed around the asynchronous and comparatively slow nature of the network. Now, those same layout and rendering engines are being shoehorned into an environment where the “server” is your local disk so it’s suddenly doing a bunch of work that was intended to be done iteratively.
Same goes the other way of course. Software designed for “native first” experiences like Flutter aren’t as popular in web dev because they work on that same, but reversed, assumption of a local disk being your source.
It would be like wondering why physical game disks aren’t popular on PC - it’s a fundamentally different technology for fundamentally different expectations and needs.
but anything built on top of web engines is going to be a little dogshit on native platforms.
Hard disagree on “little”.
Software designed for “native first” experiences like Flutter aren’t as popular in web dev because they work on that same, but reversed, assumption of a local disk being your source.
Popularity should not be dictated by what web devs prefer. As long as they build for desktop, I won’t pardon excessive resource usage. And I’m not talking about Flutter. Better performance oriented frameworks exist, see sciter.
Yep, uses CEF, though many popular desktop apps do without much perf impact.
It’s not CEF that does most of the impact. It’s the contents web devs make it load and process. And web devs generally not being very competent in optimizing is just a sad reality.
web Devs aren’t ignorant to optimizing but the kind of interfaces used in web are very different to that of desktop. Cross platform technologies can work, but anything built on top of web engines is going to be a little dogshit on native platforms.
Web tech was designed around the asynchronous and comparatively slow nature of the network. Now, those same layout and rendering engines are being shoehorned into an environment where the “server” is your local disk so it’s suddenly doing a bunch of work that was intended to be done iteratively.
Same goes the other way of course. Software designed for “native first” experiences like Flutter aren’t as popular in web dev because they work on that same, but reversed, assumption of a local disk being your source.
It would be like wondering why physical game disks aren’t popular on PC - it’s a fundamentally different technology for fundamentally different expectations and needs.
Hard disagree on “little”.
Popularity should not be dictated by what web devs prefer. As long as they build for desktop, I won’t pardon excessive resource usage. And I’m not talking about Flutter. Better performance oriented frameworks exist, see sciter.