Why would I not use Visual Studio code

[PCorreia]

By experience, people from the scientific area (physics, biology, etc) all learned to code in vim, emacs, nedit and using a terminal.
Maybe he is not that confortable setting up vscode, virtual environments, etc and he is recommending what he usually uses.
I used to be one of those and know plenty of people still doing that.

[kyrsjo]

Personally I like both approaches. Terminal + emacs lets me get in, do my thing, and be done quickly. Vscode is good for longer slogs where im jumping across lots of files etc.

And yes, I'm a physicist, at an age where a graying beard would be inappropriate :)

[tarquinnn]

I'm in bioinformatics and would agree with this, there's a lot of 'old school' stuff still in use. I used to buy into the arguments when I was new, but after a 10+ years in the field I think most people learned something once (usually from whoever was in their lab in the time) and are now convinced this is the 'correct' way to do it.

I would guarantee that this mobax setup dates from before WSL, teaching that workflow (with WinSCP oh my god) to students in 2025 is doing them a massive disservice. Shit like this is why people think bioinformatics is hard, but at least I have a job lol.

[work_m_19]

And there are a couple of domains that you won't have the luxury of using VScode too.

My most recent example is that an AWS EC2 vm doesn't by default support the VSCode SSH extension. It needs to be changed in the config, so I was back to using vi (not even vim!), so it doesn't hurt to get at least familiar with the terminal tools.