The context was that technology should evolve to fit the humans [not the other way around]. And if contemporary technology didn't have limitations, it would be correct.

But it did and humans had to adapt to the computers. Humans had to develop and learn special languages so they could communicate with computers to do all those useful things you mentioned. Why? They were limited in understanding (or parsing) human languages. It took us decades before we could talk to computers in human languages. We're getting pretty close - especially in the past few years - but there's still some friction.

We communicate with other humans using voice and three dimensional hand gestures. To use computers and early phones we had to learn to operate new input devices: keyboards and mice. Later with touchscreens we moved to two dimensional hand (finger) gestures. We're barely making voice commands work with our devices just recently.

Then, a large number of humans are figuratively tethered to their desks because the devices need power and stable internet connection. Mobile devices break this relationship a bit but you still need to charge them and be close to some sort of access point. In any case, the devices encourage sitting in one place for hours at time.

And this is just computers and smartphones. Humans adapted their entire lifestyles and transformed the landscape to cater to cars.

That aside, this is a good script you're running. Thanks.

> By default, Black uses existing trailing commas as an indication that short lines should be left separate, as described in the style documentation. If this option is given, the magic trailing comma is ignored.

https://black.readthedocs.io/en/stable/usage_and_configurati...

It should then keep the lines intact, unless they exceed the line length. I have mine set to 120.

Unless the goal was to test how well do the large language models translate solutions in prose to actionable keyboard inputs, which is pretty interesting in itself.

I mean look at the other responses here from the HN commenters. There's lots of nuance in there.

Your tables remind me of recipes in Modernist Cuisine. They all have ingredients grouped by the procedures together with weight, sometimes volume, and ratio.

Example: https://modernistcuisine.com/wp-content/uploads/2013/01/Mac-...

Take woodworking for example. When I build a kitchen cabinet, I can get lumber that's already smooth and treated, I can buy drawer tracks, I can use power tools instead of a handsaw and a screwdriver, I can use a pocket hole jig to make joints easier. I still have to do more planning and assembling than with the Ikea cabinet, which also takes more work than having a contractor do everything for me.

I'm doing it my way because it's fun for me. Other people might enjoy other parts of the process - or different things altogether.

There's a whole spectrum between doing everything from scratch and paying someone to have it done for you.

Normally instances are random within the same region, but usually there's a system in place so you can join the same one as your friend.

Damned if you do, damned if you don't.

I'm thinking about running it in a container (Podman Quadlet with systemd) behind a VPN, with daily backups with borg. Anything I'm overlooking here?

Same reason why there are different date formats, weeks start on Sundays/Mondays (or Saturdays), long/short scale numbers, drives on left/right, different wall sockets and plugs, different train gauges, and of course metric/imperial.

It's a mix of tradition, conventions, inertia.