I admit I haven’t known any Unix hackers! I guess my type of work had me assuming they would still prefer an IDE. What is it about this kind of development that makes you prefer text editors, if you don’t mind my asking?
Everything is interoperable, extensible, scriptable, and more. CLI tools are designed to run fast/instant, have keyboard shortcuts for everything, and be deeply customizable. The openness and variety cannot be overstated, Google “CLI file explorer” and you’ll easily find at least 10. Nobody has the same exact setup because it gets molded to match how your brain works. Go for popular tools, niche setups, or both.
Graphical IDEs could also run fast/instant and have keyboard shortcuts for everything, but their users don’t demand it. If you wished the file explorer/git integration/debugger/etc worked a bit differently, there might be a plugin, if you’re lucky. Many operations can only be invoked manually via sequence of dialog boxes or mouse clicks or both.
I admit I haven’t known any Unix hackers! I guess my type of work had me assuming they would still prefer an IDE. What is it about this kind of development that makes you prefer text editors, if you don’t mind my asking?
Consider the shell itself to be “the IDE”
Everything is interoperable, extensible, scriptable, and more. CLI tools are designed to run fast/instant, have keyboard shortcuts for everything, and be deeply customizable. The openness and variety cannot be overstated, Google “CLI file explorer” and you’ll easily find at least 10. Nobody has the same exact setup because it gets molded to match how your brain works. Go for popular tools, niche setups, or both.
Graphical IDEs could also run fast/instant and have keyboard shortcuts for everything, but their users don’t demand it. If you wished the file explorer/git integration/debugger/etc worked a bit differently, there might be a plugin, if you’re lucky. Many operations can only be invoked manually via sequence of dialog boxes or mouse clicks or both.