Gnome needs a react native bridge.
And considering that React Native can barely seem to keep the controls in sync on iOS and Android [0], trying to throw in a tiny minority platform like Gnome makes no sense at all. Better to build controls for raw X or even an OpenGL UI implementation. It's not like it's impossible to do the latter. [1]
In fact, VS Code already runs mostly everywhere, has gotten a huge amount of community mindshare in an amazingly short period of time, and at this point I couldn't imagine ever using gedit for...well, anything, really. Why would I?
P.S. Not a downvoter.
[0] A friend is working on a project that's run into a number of "bug on Android, not on iOS" that, once patched, became a "bug on iOS and not on Android" issue. Rinse and repeat.
I take it you've never used a Java Swing application.
Swing was, in fact, an absolute disaster.
As a dev who has used both React and a couple of native desktop UI libs, I get a fair bit of pushback on the whole Electron / app-in-browser idea. The primary concern seems to be performance, although I'm picking up an undercurrent of fear that the web stack could swallow the native realms, even if it is technically inferior, just because of the sheer inertia behind it.
In a way, Electron is a threat to the culture of the pure-native devs. Everything they know gets subsumed and disappears below the browser, and a horde of outsider devs come rushing into the native app space, with little awareness of the nuances of specific platforms and their communities.
The expansion of the industry means that those with little experience vastly outnumber those with plenty, and are highly incentivised to degrade the value of experience. That's why we see the explosion of new "frameworks", if it's only a year old then someone with one year in the industry on paper has as much "experience" as someone with 30. On paper.
That is why hardware gets faster and more reliable every year but software still gets slower and buggier. The HW side has somehow managed to keep this toxic culture in check, and their engineers, with experience on their side, are actually managing to advance their field, while the SW side keeps reinventing the wheel, a little squarer each time.
Earlier in my career, I worked primarily in a native development context. I concede in a heartbeat that Flash's buggy and insecure browser plugin was a vastly inferior user experience compared to the web standards we have now.
A platform's native tools are generally going to provide the best user experience. Mind you, they don't always provide the best DEVELOPER experience... so we're endlessly experimenting with new approaches and abstractions. But the pendulum always swings back around.
I mean, I'm fine with doing that for my favorite OS, but I'm not going to learn the details of everyone else's OS, not when I can ride above it all on a magic abstraction layer.
What? Sure you can do both.