"Can't learn" is rarely the issue. Supporting two or three separate native apps is.
For some organizations this is manageable and the right move. For others, resources need to be allocated otherwise and they take the path of least resistance.
Most non technical people don't know the difference, aren't checking ram usage, don't have philosophical opposition to writing desktop apps in a browser, etc.
If my choice was between writing real native apps and slowing development versus just getting something done, I'd choose the latter, particularly for a project like this one. I understand the complaint, but in practice it's often a developer's quibble.
i mean they call out performance issues right in the first paragraph in the readme.
terrible world of half-assed pseudo-native applications.