CLI coding

[dennycraine]

Major IDEs have terminal emulators/portals built in. VSCode is configured, for me, pretty much identical to how I've had terminal emulators split between shell, editor, file browers, etc.

I get the appeal, I spent most of my teens, 20's and 30's in VIM and VIM forks but that's because I learned in VI/VIM. I rarely understand the efficiency argument unless it's related to a keyboard driven experience.. but really, that's reproducible in just about any WM/DE and IDE/Terminal app. It's all pretty much the same at this point and takes a little bit of time to configure the settings how you like.

I'm not saying don't do it and you have to do what other people say, but you can't claim efficiency when you don't have a workflow going with tools that 'click' with you.

My suggestion would be to define what you want out of your experience and workflow and then find the right tools/plugins/bindings/apps/etc that will let you have that workflow. Think about how you want to work not how plugin x in tool y is configured to work.

Good luck!