| ▲ | rendaw a day ago |
| I think you may be right, but I think that actually enforces GP's point: if discussion was about how "a properly tuned electron could be fast", that implies an unstated general belief that electron is slow. In other words, since the time vs code was launched there was indeed a belief that electron was slow (compared to native apps). |
|
| ▲ | tcfhgj 21 hours ago | parent | next [-] |
| Even vs code is slow compared to a native app - noticable with large or many files; with search and replace in larger files (xx mb) it even crashes |
|
| ▲ | cowlevel a day ago | parent | prev [-] |
| Actually I think "properly tuned" sounds like weasel words, a no true scotsman fallacy. "Oh electron is slow? Well, it is slow, but that's not real electron, see if you were doing things the right way it would be fast" |
| |
| ▲ | tancop a day ago | parent | next [-] | | It just means Electron has bad default settings, it's hard to optimize and you might need to move some parts into C++ if you want good performance. Really the same thing as Unreal Engine, there are absolutely fast games made with it but most are super resource heavy. | | |
| ▲ | p_l a day ago | parent | next [-] | | It was not "bad default settings", like often with UE5, it was "MS did a superb job making VSCode not dog slow like Atom" and it took really lots of work | |
| ▲ | troupo a day ago | parent | prev [-] | | It means that you need a trillion-dollar company spending millions of man-hours to optimize the performance, using every trick in the book, and inventing a few new ones to deliver one optimized Electron product |
| |
| ▲ | groovy2shoes 17 hours ago | parent | prev [-] | | Combine a properly tuned config with a sufficiently smart compiler, and Electron is blazing fast! |
|