Julia Evansme: “I know Python! I've been using it on and off for like 15 years!”
also me: <still has no real idea what `setup.py` does>
(not looking for someone to explain it to me thanks)
Simon Tatham@b0rk show me someone who's used a language for 15 years and _doesn't_ have any random gap in their knowledge for a part they've never happened to run across, and I'll show you someone who's either straight-up bluffing, or doing a just-in-time web-search every time they're asked a question they don't know the answer to :-)
David Cantrell 🏏@simontatham @b0rk I’ve been using #git for over a decade and yesterday I learned about `git worktree` which is exactly what I’ve needed every day for the last four years.
@DrHyde @b0rk also, I think git is _particularly_ prone to this, because it's so broad. There are a zillion outlying git features and subcommands, and each one is useful for _something_, but a lot of them are pretty much independent of each other – you don't have to learn lots of them at once, or learn one in order to use another.
So the only way you'd ever learn all of them in advance would be by reading the entire manual … and having a _really_ good memory.
breaker-and-a-half@simontatham @DrHyde @b0rk There are also quite a few commands that need to be run infrequently enough that one doesn't automatically build the muscle memory for them, but are common and time-saving enough that learning them is still useful. I have a whole file full of useful utility features to remember that I should publish at some point. (I think Neovim appears the most in that list because editors are another type of tool that lend themselves to what you're describing.)
@breakerandahalf @simontatham @b0rk one of these years I might migrate from #vim to #neovim. But not this year.
@DrHyde @simontatham @b0rk Well. that list just includes brief cheatsheets on marks, tabpages, and folding with markers, all of which are helpful but are things I don't use enough to have an innate knowledge of (yet). I think everything in that list, however, also applies to Vim because so much of the behavior of the two editors is the same.
In my experience, the differences between the two are kind of a wash unless you really want something that only Neovim has. (Although being able to write configs in Lua is nice.)
@breakerandahalf @simontatham @b0rk yeah, every time I have to even read #vimscript, let alone write it, I get a little bit ragey.