2 ms·
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
by 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 agoAnd 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 agoI used to do this, but then found emacs/tramp and that has worked better ever since.
- zamadatix 4y agoAssuming 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.