There’s no difference between SSA and ASS in that context so it’s pointless to punish a student for that

I almost never create a tarball, so I have to look up the syntax for that. Which is as simple as man tar. But as far as extracting it almost couldn’t be easier, tar xf <tarball> and call it a day. Or if you want to list the contents without extracting, tar tf <tarball>. Unless you’re using an ancient version of tar, it will detect and handle whatever compression format you’re using without you having to remember if you need z or J or whatever.

I’ve never understood why people are so intimidated by tar

Really? Huh, TIL. I guess I’ve just never run into a situation where that was the bottleneck.

It’s safe to assume that any non-trivial program written in Go is multithreaded

That seems like a good guess, I can see why async hashing could be useful. But it would be nice if there was an alternative API that was blocking so my code wouldn’t get infected with async/await all over the place…