4 ms·

> Configuring it is starting to get old That's exactly the opposite of my experience. Since all my dotfiles are in Github, configuring new system is just a git

> Configuring it is starting to get old That's exactly the opposite of my experience. Since all my dotfiles are in Github, configuring new system is just a git clone and copying a few files around. I don't even use any config manager, since I rarely get new computers. Takes a few minutes max per machine (plus maybe package installs like zsh if it's not there already).

inanutshellus 1y ago
The original statement was "vim plugins" SO yeah you can have your fancy alias or whatever but I'm with the GP that adding a bunch of cool plugins that I get used to and then... perpetually can't use because 40% of my time is spent on remote machines I don't have admin on... ehh.. quickly becomes not worth it. It's like when I tried to get used to a DVORAK keyboard when I'd spend my weekdays in a school computer lab...
- exe34 1y ago
  You don't need admin to install emacs packages..... I'm sure vim isn't dumb enough to require that?!
  - inanutshellus 1y ago
    For me it was that each plugin would have to go through a security approval process and that was not something they appreciated. (e.g. they have "real work" to do), whilst mapping `n` to `nzz` or setting the regexpengine to `0` well, yeah, go for it.
spicycode 1y ago
Same exp here, a simple clone and setup script sorts all this in a user directory.
baobun 1y ago
> Takes a few minutes max per machine (plus maybe package installs like zsh if it's not there already). Assuming you have internet and can access GitHub. Setting up internally accessible repos for that or bake it into an image is its own excercise, which you'd have to setup again for every site and isn't there on day 0. Even so, "a few minutes per machine" builds up quickly if that happens multiple times per day and new airgapped sites are a regular occurence. That's not including the possibly larger cost of context-switching to "customization mode" for every setup. I do have a few dotfile customizations I carry around for sites/boxes I bother enough with but at this point they're cut down and familiar enough that it takes me a few seconds to put those in place manually from memory and dist defaults. Minimal .profile: VISUAL=vim EDITOR=vim tmux and some other apps will pick up on this and switch to vi-style keybindings. I resonate with embracing the Zen of leaning into defaults.

inanutshellus 1y ago

The original statement was "vim plugins" SO yeah you can have your fancy alias or whatever but I'm with the GP that adding a bunch of cool plugins that I get used to and then... perpetually can't use because 40% of my time is spent on remote machines I don't have admin on... ehh.. quickly becomes not worth it. It's like when I tried to get used to a DVORAK keyboard when I'd spend my weekdays in a school computer lab...

exe34 1y ago
You don't need admin to install emacs packages..... I'm sure vim isn't dumb enough to require that?!
- inanutshellus 1y ago
  For me it was that each plugin would have to go through a security approval process and that was not something they appreciated. (e.g. they have "real work" to do), whilst mapping `n` to `nzz` or setting the regexpengine to `0` well, yeah, go for it.

spicycode 1y ago

Same exp here, a simple clone and setup script sorts all this in a user directory.

baobun 1y ago

> Takes a few minutes max per machine (plus maybe package installs like zsh if it's not there already). Assuming you have internet and can access GitHub. Setting up internally accessible repos for that or bake it into an image is its own excercise, which you'd have to setup again for every site and isn't there on day 0. Even so, "a few minutes per machine" builds up quickly if that happens multiple times per day and new airgapped sites are a regular occurence. That's not including the possibly larger cost of context-switching to "customization mode" for every setup. I do have a few dotfile customizations I carry around for sites/boxes I bother enough with but at this point they're cut down and familiar enough that it takes me a few seconds to put those in place manually from memory and dist defaults. Minimal .profile: VISUAL=vim EDITOR=vim tmux and some other apps will pick up on this and switch to vi-style keybindings. I resonate with embracing the Zen of leaning into defaults.