[LennyWhiteJr]

This is cool and interesting, but for me it's in the same category as photography eccentrics who can develop amazing photos with a darkroom in 2021.

I'll stick with my web interface. When that doesn't suffice, I'll check out the remote branch locally and navigate around with the full power of my IDE.

[chenmike]

I feel like GUI vs. IDE misses a major part of the workflow. There's a lot to this workflow that isn't replicable on Github currently (dependency graph, frequently edited files, etc.). Navigating locally in your IDE is also part of this workflow, and yet is only one small part of what's being presented here.

[uuddlrlr]

I'd say it's closer to auto vs choosing ISO/shutter speed/f-stop.

Web tooling for git is very shallow; I wouldn't want to be without `git add/commit -p` for example.

[pjmlp]

Same here.

I was there, when cool GUIs were only available in very expensive computers, and I could buy a car or give a house entry payment with similar price points for graphical workstations.

I really don't get the point why people keep doing the extra mile to work just like we were forced to during the early days of computing.

[beermonster]

They already use terminal tools to do their dev so this is about keeping within that environment to avoid unnecessary tools or context switching. It’s always good to avoid this even if you primarily use GUI tools e.g. using plugins so you don’t need to leave VSCode for instance.

[pjmlp]

As if Alt+Tab costs that much.

VSCode by definition of being Electron based has the whole power of HTML 5 and CSS at plugins disposition.

Those terminal emulations are running on top of WebGL and canvas, while emulating a 1980's VT100 terminal.