3 ms·

They incorporate a pretty decent vim emulator as well. When I've watched people use terminals on Twitch it feels there's big periods of times spent swapping ar

They incorporate a pretty decent vim emulator as well. When I've watched people use terminals on Twitch it feels there's big periods of times spent swapping around everywhere and a whole lot of mucking around. Watching people coding real things and dealing with the various normal problems is a pretty good test of an environment, I've never seen anyone do it in compelling way where I didn't think it would be faster in an IDE. That doesn't mean it can't be done, I just haven't seen it and I've been coding for decades and have a bit of an addiction to watching people code online! There are, however, many times where it's better to go into a terminal rather than try and get things done within the IDE, but most IDEs offer the terminal as part of the experience. The only downfall of some IDEs is they have little corners of the IDE where driving them through the keyboard isn't the best experience or not fully implemented.

s_m_t 8y ago
The way I do it in vim is to have one terminal window with vim open, and one terminal with a couple of tabs for git, compiling, and flashing for embedded stuff or server for web stuff. The important part in vim is for me to start it by opening ALL the files in my project directory and then just have two side by side windows. I never muck around with the file viewer or creating new windows. So other than the commands you expect from general text editing, searching, and swapping buffers (fuzzy search plus ctags makes this comparable to the ide's I've seen) the only vim commands I use are... Focus window right, focus window left, and save. I used to waste time mucking about as you say until I saw Casey Muratori coding for handmade hero in emacs with pretty much the same setup. He takes it a step further by not even having separate buffers, he just seems to put all his code in one big file.
- keithnz 8y ago
  I'm assuming you mean https://www.youtube.com/watch?v=hbmV1bnQ-i0 https://www.youtube.com/watch?v=hbmV1bnQ-i0 ? If he's putting code into one file because it is easier to manage while using terminal based editing, that doesn't make a good case for using those tools. I've seen similar demos of peoples "enviroment", but they are all demos, not actually doing real dev. I did see https://www.twitch.tv/curlhacker https://www.twitch.tv/curlhacker ( guy who made curl ) and he worked on real issues, he worked pretty well, but I didn't see that it was any better than using an IDE...sometimes it seemed more awkward Unfortunately his coding videos have been deleted, there is one still image which shows his multi terminal setup What I like seeing is, project setup, debugging, acquiring packages, API discovery, refactoring, unit testing, navigating code / multi file management, git management, etc. Seeing developers struggle with the natural frictions that occur is much more interesting I find.

s_m_t 8y ago

The way I do it in vim is to have one terminal window with vim open, and one terminal with a couple of tabs for git, compiling, and flashing for embedded stuff or server for web stuff. The important part in vim is for me to start it by opening ALL the files in my project directory and then just have two side by side windows. I never muck around with the file viewer or creating new windows. So other than the commands you expect from general text editing, searching, and swapping buffers (fuzzy search plus ctags makes this comparable to the ide's I've seen) the only vim commands I use are... Focus window right, focus window left, and save. I used to waste time mucking about as you say until I saw Casey Muratori coding for handmade hero in emacs with pretty much the same setup. He takes it a step further by not even having separate buffers, he just seems to put all his code in one big file.

keithnz 8y ago
I'm assuming you mean https://www.youtube.com/watch?v=hbmV1bnQ-i0 https://www.youtube.com/watch?v=hbmV1bnQ-i0 ? If he's putting code into one file because it is easier to manage while using terminal based editing, that doesn't make a good case for using those tools. I've seen similar demos of peoples "enviroment", but they are all demos, not actually doing real dev. I did see https://www.twitch.tv/curlhacker https://www.twitch.tv/curlhacker ( guy who made curl ) and he worked on real issues, he worked pretty well, but I didn't see that it was any better than using an IDE...sometimes it seemed more awkward Unfortunately his coding videos have been deleted, there is one still image which shows his multi terminal setup What I like seeing is, project setup, debugging, acquiring packages, API discovery, refactoring, unit testing, navigating code / multi file management, git management, etc. Seeing developers struggle with the natural frictions that occur is much more interesting I find.