We need more zero config tools
1–10 of 74 posts
Re: We need more zero config tools
#2I don't mind configuring my tools to work for me. For example I'm a polyglot, inevitably I work with a lot of tools, IDEs, and programs. I've rigged everything so I have a lot of continuity; and context switching isn't a nightmare.
For some I use VSCode, IntelliJ, Micro or others. They all have similar(ish) shortcuts. It means I can transition so much quicker without grinding my teeth.
My point is, I don't mind configuring my tools. What I do mind, is having ease of transfer between environments, so that my configuration comes with me.
I love IntelliJ's config to cloud, it somewhat just works. It allows me to change something on the work laptop that will apply at night on my home machines. VSCode does the same now (it used to require a plugin and github).
Micro and other tools use a ~/.config/subfolder which also works, I use git to pass stuff around various computers, with various degrees of success.
My .zhsrc / .profile is carried around and I have all my 2-3 letters aliases that do complex things, so I don't need to remember everything. This is a powerful way to be very productive very easily. And if you forgot how it works, just read the file. The amount of time where I saw a senior professional waste time re-googling the same thing over, or fumbling around their shell history has boggled my mind. ref. [1]*
If you're a professional, chances are you're going to cart your configs and settings with you for many years to come. So make it as portable as possible.
Even my lazygit is configured. One time, I got a new job, I left it as default... and forced push changes by mistake (because it's not turned off by default and very easy to fat finger it), and that caused a lot of grief. So be careful about acting proud in being 'zero config'.
I'd recommend being efficient, not a purist in search of minimalism. It also shields you from upstream software changing their default on a whim.
Re: We need more zero config tools
#3I don't mind configuring my tools to work for me. For example I'm a polyglot, inevitably I work with a lot of tools, IDEs, and programs. I've rigged everything so I have a lot of continuity; and context switching isn't a nightmare. For some I use VSCode, IntelliJ, Micro or others. They all have similar(ish) shortcuts. It means I can transition so much quicker without grinding my teeth. My point is, I don't mind confi…
For managing config files I use yadm https://yadm.io/, which I learned of on HN.
Among other great features, it lets me tailor settings per OS (Windows, Mac, Linux) and per client. And my settings are all in git, so they’re easy to save and copy around, and they’re all in one place, not dependent on each tool to know how to save their settings on some server.
Re: We need more zero config tools
#4I know this will be unpopular but I try to live a zero-config life. I just live with the defaults 99% of the time. I prefer not to be beholden to some special keyboard map or shell config or that essential plugin that does something very niche that you could simply not live without any more, because what if you do need to live without it?
If you ever change machine or do pair programming or whatever where you are not using your highly-tweaked config, and you are essentially a frustrated jibbering wreck and barely more competent than a 3 year old using a computer for the first time because there is only vi and not Emacs, or your "essential" key bindings are not there or your "essential" plugins are not there or horror of horrors it is vanilla bash and not zsh with your 9000 line config file.
These days I have learnt to abandon the configs, and learn to love the default life. Just open a vanilla laptop and guess what, it already has "your" config since they are all the defaults! Spend that mental energy and time on something else and get stuff done.
Re: We need more zero config tools
#5Zero config tools are quite excellent. I include quite a few of them in https://github.com/hiAndrewQuinn/shell-bling-ubuntu , although I also include high-config stuff in there at well so people can compare and contrast - you've got `hx` right next to a fully decked-out `nvim`, for example.
Re: We need more zero config tools
#6I know this will be unpopular but I try to live a zero-config life. I just live with the defaults 99% of the time. I prefer not to be beholden to some special keyboard map or shell config or that essential plugin that does something very niche that you could simply not live without any more , because what if you do need to live without it? If you ever change machine or do pair programming or whatever where you are no…
Not always makes sense, especially when the defaults are counterintuitive.
Example: I never understood why tmux folks have chosen different key bindings than screen, as their product was meant to replace screen, not to be run like one inside another. But the brain has been wired over the years. Then I am always remapping tmux to ctrl-a.
There are also other examples when defaults have been made to satisfy some perceived but unrealistic expectation.
Re: We need more zero config tools
#7Article links to Julia Evans’ blog post on fish as well, which is a good read. https://jvns.ca/blog/2024/09/12/reasons-i--still--love-fish/
Re: We need more zero config tools
#8I don't mind configuring my tools to work for me. For example I'm a polyglot, inevitably I work with a lot of tools, IDEs, and programs. I've rigged everything so I have a lot of continuity; and context switching isn't a nightmare. For some I use VSCode, IntelliJ, Micro or others. They all have similar(ish) shortcuts. It means I can transition so much quicker without grinding my teeth. My point is, I don't mind confi…
For managing config files I use yadm https://yadm.io/ , which I learned of on HN. Among other great features, it lets me tailor settings per OS (Windows, Mac, Linux) and per client. And my settings are all in git, so they’re easy to save and copy around, and they’re all in one place, not dependent on each tool to know how to save their settings on some server.
Have you used Chezmoi (https://chezmoi.io) before? I've been using that for a few years now; I'd be curious to understand how YADM compares.
Re: We need more zero config tools
#9I know this will be unpopular but I try to live a zero-config life. I just live with the defaults 99% of the time. I prefer not to be beholden to some special keyboard map or shell config or that essential plugin that does something very niche that you could simply not live without any more , because what if you do need to live without it? If you ever change machine or do pair programming or whatever where you are no…
Not always makes sense, especially when the defaults are counterintuitive. Example: I never understood why tmux folks have chosen different key bindings than screen, as their product was meant to replace screen, not to be run like one inside another. But the brain has been wired over the years. Then I am always remapping tmux to ctrl-a. There are also other examples when defaults have been made to satisfy some percei…
I can't speak to specifics of tmux/screen but, generally, one approach to this problem is to pick tools with the defaults you want. If a tool doesn't have good defaults, pick one that does. Sure, you have to be pragmatic about this—if no tool has good defaults, just pick the one with the best (and the best support for configuration...)
Re: We need more zero config tools
#10I know this will be unpopular but I try to live a zero-config life. I just live with the defaults 99% of the time. I prefer not to be beholden to some special keyboard map or shell config or that essential plugin that does something very niche that you could simply not live without any more , because what if you do need to live without it? If you ever change machine or do pair programming or whatever where you are no…
Defaults are fine if you live a default life.
I moved to another country 15 years ago, but I was never going to learn a different keyboard layout after having already been quite proficient in my previous one. And if I use e.g. a Mac at work and Linux at home, I want certain special characters to be available with the same key combinations (for some reason, that's not the case by default), otherwise I'll just confuse myself.