4 ms·
For me, those are ancient tools for ancient times, designed when things really were different. We have other capabilities now, nobody is forced to work on the C
by 9dev 4y ago
For me, those are ancient tools for ancient times, designed when things really were different. We have other capabilities now, nobody is forced to work on the CLI anymore - I also refuse to spend weeks to „master“ my editor.
Typing code is literally the least bad thing slowing me down when creating software.
- wruza 4y ago“Ancient” with regard to a living thing is usually a characteristic that shows an ignorance of features and a lack of experience with dynamics of toolsets. Truly ancient (obsolete) things get lost to history. We have other capabilities now, nobody is forced to work on the CLI anymore - I also refuse to spend weeks to „master“ my editor I agree with all of that, but from the vim side of things. Although these are not my main concerns with organizing a development process, I find it troublesome to set up and tune a modern IDE into a useful state either, and refuse to do that unless it’s a workplace requirement. Typing code is literally the least bad thing slowing me down when creating software. Typing code in vim-insert or emacs is the same as in any other editor. You press keys, they show up on the screen. Press F1 and type a command. Press a shortcut to enter files pane and select a file to edit. Press C-K C-9 to expand all user folds. Install a plugin, map some keys and now you can set and cycle through bookmarks easily.
- skydhash 4y agoIt’s not about typing faster. It’s about learning a language of editing. When you’re begin to be fluent in it, you will be communicating with the editor the changes you want to see. And it’s just a terse language that realizing what you want to actually do it and see it done take only one or two seconds. I strongly believes the “Think about it” -> “Express it” -> “See it done” is much better the whole ballet your hand would be doing with the mouse and keyboard.