I mean, in a Node project, if I need some internal CLI tool, I'll just write a Node script. But for distributable apps, doesn't make much sense to me either.
I don't read the parent comment as saying that vscode shouldn't be written in electron. I read it as the opposite, that they are defending the terminal emulator using electron.
Also, out of interest, what reasons would you give for vscode being written with electron?
I read it as sarcasm, cause writing a terminal emulator in electron is really a stretch, could be wrong ofc.
At first I was a bit irritated that vscode is build on electron. Then I found code-server, essentially vscode in the browser and fell in love with it. I can run a fully fledged IDE on a PI without using too much ram or CPU power because the client does a lot of the ui heavy lifting.
Then also the other way around, I use code-server on my powerful tower pc and can connect to it via vpn to run heavy coding tasks directly on the server while not miss8ng a single IDE feature. I use the metals plug-in to code Scala backend services and it works incredibly well. Much better then using remote desktop applications (nomachine, vnc, xrdp etc.) on the go. It's even better then ssh when the connection is bad, like mosh but for ui.
That's definitely not true. While fonts may be the same, colours are definitely not. Many terminals support a very large array of colours. Lots of tools have animations for progress bar, and a shell us no guarantee of being responsive. Anything that displays git statuses in the prompt will take multiple seconds to be ready on a large project, and many will just silently pause while they chug away at whatever they're doing.
In terms of responsiveness, there are plenty of terminal based apps that respond poorly to window resizing (the flickerkng is incredibly frustrating to me), or just don't handle aspect ratio changes at all and clip the ends of lines. Some tui applications don't clear their screen buffer properly on quit so completely break scrolling back the terminal. Many terminals really suck for performance and can really really chug if you accidentally dump a large JSON file to the terminal, for example. That's not responsive at all.
Also, natural language is a better command interface than iconic point and click for intermediate to advanced users. The mouse studies that came out of Apple back in the day were based on testing against the mass market so their findings only apply to mom, pop, buddy and sis.
Have there been studies done on "advanced users"? I'm an advanced user and I think mouse based interfaces are great when mixed sensibly with keyboard shortcuts and command search (like VSCode's Ctrl-Shift-P).
I'm not going to ever use the Edit->Copy menu but I'm also not going to learn the shortcut to click the Ublock origin button in Chrome, which I do maybe once a month.
Do you have any evidence for your assertion? It sounds like snobbery.