3 ms·

This is the same reason I eventually learned and stuck with Vi(m). Implementing a project on a massive array of SPARC Solaris boxes and every "easy' tool I'd le

This is the same reason I eventually learned and stuck with Vi(m). Implementing a project on a massive array of SPARC Solaris boxes and every "easy' tool I'd learned just... wasn't there. I had kind of learned Vi at that point, but wasn't remotely proficient in it, and had only gotten as far as I had due to a bunch of cool plugins I'd installed that definitely weren't available.

zamadatix 4y ago
That last part is often forgotten. I usually stick with defaults (or as close as I reasonably can) not because they are functionally better but because for most things I don't have the return on learning and regularly using two instances of ${tool} isn't worth the extra time. Sometimes it's a pain but it seems to pay off.
- deafpolygon 4y ago
  And when I'm doing something on my local machine - very often, a more modern tool is required anyway. (Visual Studio in the case of C#/C++, and VS Code is infinitely quicker and simpler to get up and going with when editing other source code).
- ParetoOptimal 4y ago
  I used to do this, but then found emacs/tramp and that has worked better ever since.
  - zamadatix 4y ago
    Assuming everything you connect to has a remote file interface and you only use your computer affords many conveniences. Knowing the default tool first is for when those don't hold, not for when you need to do something from your machine.
scns 4y ago
That is a good point. But Nu offers someting else: > First and foremost, Nu is cross-platform. Commands and techniques should work across platforms and Nu has first-class support for Windows, macOS, and Linux. Source: GitHub. No snark intended.
IshKebab 4y ago
Nano is fairly commonly installed mercifully. Micro (which is an actually "normal" terminal editor) is becoming more popular too and is also trivial to install (since it is written in Go).

3 ms·

This is the same reason I eventually learned and stuck with Vi(m). Implementing a project on a massive array of SPARC Solaris boxes and every "easy' tool I'd le

by bmelton 4y ago

zamadatix 4y ago
That last part is often forgotten. I usually stick with defaults (or as close as I reasonably can) not because they are functionally better but because for most things I don't have the return on learning and regularly using two instances of ${tool} isn't worth the extra time. Sometimes it's a pain but it seems to pay off.
- deafpolygon 4y ago
  And when I'm doing something on my local machine - very often, a more modern tool is required anyway. (Visual Studio in the case of C#/C++, and VS Code is infinitely quicker and simpler to get up and going with when editing other source code).
- ParetoOptimal 4y ago
  I used to do this, but then found emacs/tramp and that has worked better ever since.
  - zamadatix 4y ago
    Assuming everything you connect to has a remote file interface and you only use your computer affords many conveniences. Knowing the default tool first is for when those don't hold, not for when you need to do something from your machine.
scns 4y ago
That is a good point. But Nu offers someting else: > First and foremost, Nu is cross-platform. Commands and techniques should work across platforms and Nu has first-class support for Windows, macOS, and Linux. Source: GitHub. No snark intended.
IshKebab 4y ago
Nano is fairly commonly installed mercifully. Micro (which is an actually "normal" terminal editor) is becoming more popular too and is also trivial to install (since it is written in Go).