right? I don’t watch TV because of all this crap. I don’t understand how some people have the patience, honestly.

and in most cases that’s not good enough to justify choosing c

How did Python end us as Phlegm? It’s one of the chillest languages to write, definitely blood

I counted it too and it’s accurate

(in case the reader needs more data points)

I’ve known Zed for almost a year now, but it still lacks a lot of what VS Code offers. Especially when it comes to customization.

> Welp, that precisely recreated it -- even identical shas! Looking at
> the b4 output, I do see a suspicious "39 commits" listed for some reason.

Well, that's the point where the user, in theory, goes "this is weird, why is
it 39 commits," and does Ctrl-C, but I'm happy to accept blame here -- we
should be more careful with this operation and bail out whenever we recognize
that something has gone wrong. To begin with, we'll output a listing of all
the commits that will be rewritten, just to make it more obvious when things
are about to go wrong.

> So, I assume the "git-filter-repo" invocation is what mangled it. I will
> try to dig into what b4 actually asked it to do in the morning...

Thanks for looking into this. Linus, this is accurate and I am 100% convinced
that there was no malicious intent. My apologies for being part of the mess
through the tooling.

I will reinstate Kees's account so he can resume his work.

-K

clearly the bed

Last time I did, it was thanks to canonical pushing snaps and other things no one asked for.

as a sommelier or as an avocado?

Your innie excels at getting reactions from his peers

how naive of him to think companies didn’t already scrape his facial data from anywhere he might have had a picture 10 years ago

sir, this is a wendy’s

on second though: “ugh, light mode”

I want to convert all lossless files to lossy, preferably before uploading them

so it’s not exactly a mirror, right?

here’s an idea:

• A - the source containing lossless files
• B - the local storage of lossy files
• C - a remote mirror of B

With that, you can do:

• A -> B: a systemd service that makes this conversion.
• B -> C: git or syncthing to mirror and/or version control.

This uses more storage than you probably intended to (lossy files are also stored locally), but it’s a mirror.

the best thing is when not even the author knows the correct order of running the cells; because of course it isn’t top-to-bottom.

The if block is still in the global scope, so writing the code in it is a great way to find yourself scratching your head with a weird bug 30 minutes later.

I work in an academic / research environment. Depending who wrote it, even seeing a __name__ == "__main__" is a bit of a rare thing…

everyone knows viruses are allergic to apps

It seems pcm-memory can do it on Intel CPUs and uProf for AMD.

Other than these I’ve mostly seen benchmarking and profiling tools (like perf) but I guess these are not what you’re looking for.

Is that for a specific process or the system?

yeah, that’s… one of the points in the article