This leapt out at me as well. Given the quote "some evenings", I'd put some money on him actually doing this near enough every day. And given the man was still doing this approaching 50, I'd put a bit more money on him having been doing this for, like, 25+ years.
If you want to maximize the chances of your weed habit causing you problems, this is exactly the sort of weed habit you should develop.
Hm, that's a good point. I totally did not think of that as a possibility. But what are the chances? I mean, it's just a cute little pit bull we're talking about here! It's not as if it's even a big dog, like a golden retriever, or a nice friendly alsatian.
I can totally understand why. I tried fixing ag around the time Ripgrep was first published and once I learned about rg I never looked back.
On a related note, it's now ten years since an everyday tool written in Rust was released and Rust is still seen as a scary new language that might turn out to be a quick fad.
The local account tip is a good one. I used it when setting up Windows 11 Pro on my desktop PC.
Regarding updates: you might not even need to think about registry keys! I found these Windows 10 group policy settings to work well for many years: https://news.ycombinator.com/item?id=18157968 - and I'm still using them with Windows 11, near enough, though it seems you now need to go to "Windows Update\Manage end user experience" to find the Configure Automatic Updates setting I mention.
(I've also switched to using option 2 (Notify for download and auto install) rather than 3 (Auto download and notify for install), on the basis that it sounds safer, and I've had no problems from doing that. Not to say that I actually remember having any problems from letting Windows download the updates ahead of time! - but I'm comfortable living dangerously.)
You're sort-of right, I think, because you do need an Apple account to sign in to the Mac App Store to get current Xcode in the first place - but the $99 is entirely optional!
For distributing your program without the fee, you'll probably moan about the hoops that people have to jump through to run your stuff: https://support.apple.com/en-gb/guide/mac-help/mh40616/mac - and I can't say I love this myself, but people can run your stuff, and no fee necessary.
(I've got a couple of (somewhat niche) FOSS things for macOS, and I build the releases using GitHub Actions with whatever default stuff the thing uses, then make up DMGs that people can download from the GitHub releases page. I added a bit in the documentation about visiting the security dialog if you're blocked - and that seems to have been sufficient.)
The Emacs interface in general isn't massively like Lotus 1-2-3's, but magit's somewhat is. The above post goes into a bunch of detail, but what I remember most about my time using 1-2-3 (a long time ago now) was that the shortcuts were super easy to get accustomed to, because there was a prompt of some kind every step of the way. magit's rather similar prompts work well in this respect too. (Though you do still have to know how to use git. This is git, after all.)
Where there might be some more general overlap with Emacs: an apparent goal of Lotus 1-2-3 was, like Emacs, that its users would be able to automate it, and without too much bother given their knowledge of how to operate it in general. It's actually better than Emacs in this respect, because the macros seemed to be largely based on the keys you press; Emacs, by contrast, makes you jump through some hoops to figure out what the corresponding elisp for some sequence of keys might be. (The hoops are not hard to jump through! But they are there.)
(Along similar lines: Autodesk's Maya. And, to an extent, 3D Studio Max - though the scriptability there felt merely comprehensive, rather than pervasive. MaxScript was measurably less horrid than MEL though.)
If you want to maximize the chances of your weed habit causing you problems, this is exactly the sort of weed habit you should develop.
reply