4 ms·
Moving on from the same tired argument that pops up in every thread concerning this topic... if the Qt crowd really cares about this (be it memory usage, etc),
by Klonoar 9y ago
Moving on from the same tired argument that pops up in every thread concerning this topic... if the Qt crowd really cares about this (be it memory usage, etc), you'd think they'd do more to say, make React Native just compile down to Qt.
There's even project(s, or at least one) out there that seem to have had this idea (https://github.com/status-im/react-native-desktop https://github.com/status-im/react-native-desktop), but few people working on them. I would be 100% unsurprised to see no Electron people doing this, so if you really want to see an alternative, and are looking for cool open source projects to devote time to, maybe something worth considering. It's not an easy feat at all - this thread alone (https://github.com/status-im/ideas/issues/34 https://github.com/status-im/ideas/issues/34) kind of explains why.
In my opinion, this is unlikely to ever take off in any serious form, and Qt will continue to generally be the "it exists but nobody really considers it unless Electron is 100% out of the question" option. There's simply too much momentum in terms of new UI components/capabilities/what-have-you that the browser runtime brings to the table that Qt (be it SDK or community built components) cannot match.