Earlier quoted context omitted.
> scientific software ... where interfaces are notoriously bad. I think the problem here is two fold: bad UIs and bad APIs. In the science world, there doesn't seem to be any abstraction between backend and frotnend -- the whole thing is one intertwined mess. Scientists don't always write great software; they write scripts that get the job done quickly in a very specific way. Pair that with the lack of time that they…
How is Electron doing btw? I'm itching to use it in one project but it doesn't feel like it's getting any traction in the community for a long time now. Since it's a long term project I kind of get mixed feelings about using it.
What makes you say that it isn't getting traction? AFAIK, some huge companies are using it to create their apps.
I think it gets a lot of underserved hate, just because it's JS and because it isn't "truly native". People also love to chime in about its performance but 9/10 times that's down to a bad implementation, in my humble opinion.