Yep, learned it recently from a list of things that are, surprisingly, named after real people. Deb and Ian eventually got married but are now divorced.

It’s so out of date that Deb and Ian are no longer together

(…this is actually true, not just a joke)

Yeah, that part is pretty wild and definitely Microsoft’s fault.

The Crowdstrike problem was in fact a Crowdstrike problem. It affected Linux too, but of course there are vastly fewer users of Crowdstrike on Linux: https://www.google.com/amp/s/www.theregister.com/AMP/2024/07/21/crowdstrike_linux_crashes_restoration_tools/

This is pretty obviously a Microsoft problem.

What were the issues you’ve had with WSL? I’ve been happily using that for a while now.

Regular vim has that (as a compile option, like most of its features).

Why do you think most early adopters use Windows exclusively?

Seconded. Wezterm seems to have a similar level of features and customizability as Kitty, but with Lua as its config/extension language. I migrated from Alacritty rather than Kitty, so I don’t know how Kitty’s speed compares, but I haven’t missed Alacritty, which is honestly saying something.

I think you missed the last sentence of the post:

Finally, when you reference a Git hash for posterity, e.g. in another commit message, I’d recommend always using the full value.

The git config is just for display purposes in terminal output. That only needs to be unique as of the time it’s displayed; and as I noted, the current default behavior is to adjust the size dynamically, so the displayed hash segment is always unique no matter how big the repo is.

I’m not sure I understand what issue Linus et al. are trying to solve. If the full hash is used whenever a commit reference is saved somewhere, then why does it matter how core.abbrev is configured? In particular, why use a static value, when git’s default behavior is to compute a value based on the current number of objects in the repository? (Edit: just noticed this post is over 10 years old. Maybe git didn’t have this automatic default behavior back then.)

For what it’s worth, jj has an even better solution, which is to highlight the shortest unique prefix in each specific hash it displays.