The number of times I move code around and can just press a hotkey to fix indentation though. Not possible with Python.

Except it clearly doesn’t produce the same result every time. You’re not making a good case for whatever you’re trying to say.

Yeah, it’s accurate both ways

Postgres doesn’t need that much ram IMO, though it may use as much as you give it. I’d reduce it’s ram and see how performance changes.

Yeah in a PR I would probably reject this for being too clever. Before clicking I expected the image to start at 100mb or more, but it’s already under 50, who cares at this point?

Why no real db? Those other 2 features make sense, but if the only option you can use sacrifices the 3rd option then it seems like a win. Postgres is awesome and easy to backup, just a single command can backup the whole thing to a file making it easy to restore.

1 is just not true sorry. There’s loads of stuff that only work as root and people use them.

About the trust issue. There’s no more or less trust than running on bare metal. Sure you could compile everything from source but you probably won’t, and you might trust your distro package manager, but that still has a similar problem.

Except lots of email services won’t take a technically correct email anyway.

QML on the other hand is awesome imo.

There’s dotnet format which will format your code. You can configure it with editorconfig

I like how Java uses it. As a C# dev I wish for it sometimes.

I use a k8s Cron job to execute backups with Kopia. The manifest is here

I don’t like the idea of replacing one well known YAML schema (k8s as much as I hate it is well known), with another YAML schema that is not well known. I think I’d rather use something to get away from YAML altogether, rather than just trade one for another. The reason helm and kustomize work well is that your existing k8s resource knowledge transfers, it sounds like it wouldn’t with this thing.

I’d keep going until you see it again and try to solve it then. I wouldn’t report an issue that you can’t reproduce, some projects refuse to accept issues without a repro. Sometimes something weird happens and you don’t know why and you’ll never know, you just need to move on and keep building, if it’s a real problem it’ll come back.

Yeah but performance has way more to do with architecture than it does code readability. It doesn’t matter how well you write your code, if it’s an electron app it’s going to use more ram than a native app. So I totally agree, but at the scale that it’s a real problem it has more to do with architecture than the code in any given function.

I only use it to clone projects via the Open in GitHub desktop link.

This is the way

Been using it for years it’s great

Uh… If they messed with the iso, they could very easily mess with the NFO