3 ms·
Because Electron is heavy and clunky. It makes no sense for a simple wrapper around a tiny (less than 1MB) commandline tool to have memory and CPU requirements
by kitsunesoba 11y ago
Because Electron is heavy and clunky. It makes no sense for a simple wrapper around a tiny (less than 1MB) commandline tool to have memory and CPU requirements on par with those of an instance of Chromium with a javascript-laden page open in a tab.
- onewordnowait2 11y agoDownloaded it, libcef.dll + many other MBs of browser. But no nodejs. Weird.
- yellowapple 11y agoIf it's really just a wrapper around the git command, then I suppose I'm not really interested anyway, then, seeing as the existing Git GUIs for Linux provide that rather well. I was assuming it was like the Mac client where it provides Github-specific functionality (adding "Clone in Desktop" buttons to repo pages, managing pull requests, etc.).
- kitsunesoba 11y agoI was assuming it was like the Mac client where it provides Github-specific functionality (adding "Clone in Desktop" buttons to repo pages, managing pull requests, etc.). It is like the Mac client, but that functionality still doesn’t justify the resource usage than a Chromium wrapper would bring.
- yellowapple 11y agoRight; my point with that was more around the implication that it's just a git wrapper. Regardless, my ultimate point is that Github went through all this trouble to make this Electron Shell thing and they don't even bother using their own tool. That seems surprising, Electron's merits and troubles aside.