You conveniently forget about the DOM, for example
Re:Leaving The Qt Company
by SemanticStrengh on Wednesday May 18, 2022 @01:56PM
(#31425692)
I'm not seeing why the DOM would necessarily makes rendering slower.
See e.g. this comparison showing react web being faster and more energy efficient than react-native.
https://ionicframework.com/blog/ionic-vs-react-native-perfor...
It's true that pathological DOM dynamism might incur some cache/layout invalidations, however if that were to be an issue (which is very rare and profiling is easy), you could mostly eliminate the problem with a few lines of https://developer.mozilla.org/en-US/docs/Web/CSS/contain
What does it feels like to spit random beliefs out of your hat and state them as truth? Native doesn't even mean anything, there really is something wrong going on on the mental models people have when talking about GUIs. IIRC QT use GDI+ on Windows for drawing 2D GUIs, which is mostly CPU based. And its shows in many tasks, see e.g. the strokePoly40 https://blend2d.com/performance.html Chromium use Skia and gecko use webrender, those are much much much faster on average. In fact the web has more FPS than native libraries in general.