Another of those articles assuming a program with a GUI can't have keyboard shortcuts, configuration stored in human readable config files or composition with other external programs...
> An IDE limits you to the extent of what their creators envisioned you would want to do.
> Being comfortable in a terminal means speaking the same language as the machine does.
No, the terminal and all the programs you start in it usually run on the same abstraction level as a GUI.
> Configuration for terminal programs is also extremely portable
And GUI application configurations are inherently not?? VSCode config is stored in a single json file?
> Dotfiles are human readable and contain plain-text. They also become much less coupled with your projects than IDE configurations would be. When you use an IDE configuration file to describe how the computer should build your code you enforce everyone in your team to use the same tool.
Another invalid assumption that an IDE specific config file is not human readable, so let's replace it with a vim specific config file instead! (because vim is not an IDE?) Anyway, best practice nowadays is for IDEs to simply open the standard build-description file out of the box, eg CMakeList.txt or build.gradle.
> Finally, being proficient with a terminal is a “learn-once-use-everywhere”
Hold on a minute, i just have to copy all my vim-config files, plugins, bashrc-files and workarounds for even basic functionality such as copy-paste in tmux to work? Also good luck using PowerShell or cmd on Windows if you are a die hard linux user. VSCode, Sublime and IntelliJ behaves much more alike across Win/Linux/Mac than respective terminals. While true that being productive on a remote ssh shell is an important skill it has very little to do with what the article describes.
> An IDE limits you to the extent of what their creators envisioned you would want to do.
10000+ VSCode plugins disagree with you https://marketplace.visualstudio.com/vscode
> Being comfortable in a terminal means speaking the same language as the machine does.
No, the terminal and all the programs you start in it usually run on the same abstraction level as a GUI.
> Configuration for terminal programs is also extremely portable
And GUI application configurations are inherently not?? VSCode config is stored in a single json file?
> Dotfiles are human readable and contain plain-text. They also become much less coupled with your projects than IDE configurations would be. When you use an IDE configuration file to describe how the computer should build your code you enforce everyone in your team to use the same tool.
Another invalid assumption that an IDE specific config file is not human readable, so let's replace it with a vim specific config file instead! (because vim is not an IDE?) Anyway, best practice nowadays is for IDEs to simply open the standard build-description file out of the box, eg CMakeList.txt or build.gradle.
> Finally, being proficient with a terminal is a “learn-once-use-everywhere”
Hold on a minute, i just have to copy all my vim-config files, plugins, bashrc-files and workarounds for even basic functionality such as copy-paste in tmux to work? Also good luck using PowerShell or cmd on Windows if you are a die hard linux user. VSCode, Sublime and IntelliJ behaves much more alike across Win/Linux/Mac than respective terminals. While true that being productive on a remote ssh shell is an important skill it has very little to do with what the article describes.