11 ms·

If you think $80 dollars is too much for a tool that you can expect to use for 5+ years without issues (I'm at 5 years with Sublime currently), I don't know wha

If you think $80 dollars is too much for a tool that you can expect to use for 5+ years without issues (I'm at 5 years with Sublime currently), I don't know what to tell you. If you work a trade, you should expect to invest in high quality tools (a laptop, maybe a second monitor, etc.). Granted, if I knew how to as productive as I am with Sublime Text with Vim or Emacs, I would switch over in a heart beat.

frosted-flakes 8y ago
He didn't say it was too much, only that it was more than other comparable editors. If all else is equal, why wouldn't you take the cheaper option?
- rajangdavis 8y ago
  Vim and Emacs may work for GP's workflow, but I can't say the same for me (at this time). In that context, I would say that cheaper doesn't always mean better (I prefer to be productive than bill for learning new tools unless that is part of the project). I tried working with Vim exclusively when I started my job ~2 years ago, and my terminal would hang quite often that I had to abandon it (I use ConEmu which is free, but hangs quite often). I also work on a Windows machine and do not want to use the windows command line, I prefer git-bash/mingw32.
  - nickjj 8y ago
    I'm currently using Windows with WSL + wsltty + tmux + terminal vim with no issues. Things are really fast and stable. I often have 10 Vim instances open across half a dozen tmux sessions. Each one takes up about 8mb of RAM with ~40 plugins doing everything I could ever ask for in a code editor. The only time they get closed is when Windows decides to reboot but then I can automatically restore the tmux sessions with 1 hot key. I switched to Vim last month after I found VSCode to be unusable for editing a 1mb a markdown file (it used over 50% of my i5 3.2ghz quadcore just idling with the file open). I wrote about the experience at https://nickjanetakis.com/blog/vim-is-saving-me-hours-of-work-when-writing-books-and-courses https://nickjanetakis.com/blog/vim-is-saving-me-hours-of-wor.... Haven't looked back since.
    - rajangdavis 8y ago
      I have an i3 so I might not have as awesome experience as you may have... had to optimize for longer battery life because I was traveling a fair bit at the time of purchase. I'm looking to change jobs, so hopefully when I end up somewhere new, I can get a new laptop and try to start with vim. After reading @frosted-flakes comment, I was messing around a bit with vim yesterday, but went back to Sublime because of familiarity with commands for navigating through files. I'll get to vim one day, just happy with where I am at now. Was reading through your article and noticed your comment about managing windows in Windows. Did you try using the windows key + left (or any of the other directions)? Here's a video of that: https://www.youtube.com/watch?v=fxerpQ8WK8Y https://www.youtube.com/watch?v=fxerpQ8WK8Y
      - nickjj 8y ago
        I'm on an i5 3.2ghz from around 5 years ago but most slowdown issues with WSL will be I/O bound, not CPU (unless you happen to be compiling code a lot). Yeah I use the window key + arrow key shortcuts a lot but it's not the same as a dedicated window manager. Thanks though.

frosted-flakes 8y ago

He didn't say it was too much, only that it was more than other comparable editors. If all else is equal, why wouldn't you take the cheaper option?

rajangdavis 8y ago
Vim and Emacs may work for GP's workflow, but I can't say the same for me (at this time). In that context, I would say that cheaper doesn't always mean better (I prefer to be productive than bill for learning new tools unless that is part of the project). I tried working with Vim exclusively when I started my job ~2 years ago, and my terminal would hang quite often that I had to abandon it (I use ConEmu which is free, but hangs quite often). I also work on a Windows machine and do not want to use the windows command line, I prefer git-bash/mingw32.
- nickjj 8y ago
  I'm currently using Windows with WSL + wsltty + tmux + terminal vim with no issues. Things are really fast and stable. I often have 10 Vim instances open across half a dozen tmux sessions. Each one takes up about 8mb of RAM with ~40 plugins doing everything I could ever ask for in a code editor. The only time they get closed is when Windows decides to reboot but then I can automatically restore the tmux sessions with 1 hot key. I switched to Vim last month after I found VSCode to be unusable for editing a 1mb a markdown file (it used over 50% of my i5 3.2ghz quadcore just idling with the file open). I wrote about the experience at https://nickjanetakis.com/blog/vim-is-saving-me-hours-of-work-when-writing-books-and-courses https://nickjanetakis.com/blog/vim-is-saving-me-hours-of-wor.... Haven't looked back since.
  - rajangdavis 8y ago
    I have an i3 so I might not have as awesome experience as you may have... had to optimize for longer battery life because I was traveling a fair bit at the time of purchase. I'm looking to change jobs, so hopefully when I end up somewhere new, I can get a new laptop and try to start with vim. After reading @frosted-flakes comment, I was messing around a bit with vim yesterday, but went back to Sublime because of familiarity with commands for navigating through files. I'll get to vim one day, just happy with where I am at now. Was reading through your article and noticed your comment about managing windows in Windows. Did you try using the windows key + left (or any of the other directions)? Here's a video of that: https://www.youtube.com/watch?v=fxerpQ8WK8Y https://www.youtube.com/watch?v=fxerpQ8WK8Y
    - nickjj 8y ago
      I'm on an i5 3.2ghz from around 5 years ago but most slowdown issues with WSL will be I/O bound, not CPU (unless you happen to be compiling code a lot). Yeah I use the window key + arrow key shortcuts a lot but it's not the same as a dedicated window manager. Thanks though.