• folkrav@lemmy.ca
    link
    fedilink
    arrow-up
    19
    arrow-down
    3
    ·
    edit-2
    1 year ago

    I’d rather optimize for the 99% case, which is me getting shit done on my machine, than refuse to use convenient stuff for the sake of maybe not forgetting a command I can perfectly just look up if I do legitimately happen to forget about it. If I’m on a remote, I already don’t have access to all my usual software anyway, what’s a couple more aliases? To me this sounds like purposefully deciding to slow yourself down cutting paper with a knife all the time cause you may not have access to scissors when you happen to sit at someone else’s desk.

      • folkrav@lemmy.ca
        link
        fedilink
        arrow-up
        6
        arrow-down
        1
        ·
        1 year ago

        I do connect to VMs and containers all the time, I just don’t see a reason not to speed myself up on my own machines because of it. To me, the downside of typing an alias on a machine that doesn’t have it once in a while, is much less than having to type everything out or searching my shell history for longer commands every single time. My shell configs are in a dotfiles repo I can clone to new personal/work machines easily, and I have an alias to rsync some key parts to VMs if needed. Containers, I just always assume I don’t have access to anything but builtins. I guess if you don’t do the majority of your work on a local shell, it may indeed not be worth it.