> That said: I think we should. Electron is problematic and you can always tell an Electron app when you see it because the performance is so terrible. Is this

> That said: I think we should. Electron is problematic and you can always tell an Electron app when you see it because the performance is so terrible. Is this intrinsic to Electron architecture --- or just the current realities of the sort of JS people tend to write, thrown at the JS engine that Electron wraps? What I mean, if the final executable is actually some sort of embedded Python interpreter and "Electron" is a bunch of shoddy Python scripts messing with WebKit and Gtk/Tk/Qt/whatever then I'd steer clear. But if the non-3rd-party parts are solidly high-perf-engineered, I'll remain interested..