Dave Vasilevsky

This is because the parallel_compression example builds against the static library, which [builds by default with multi-threading off](https://github.com/facebook/zstd/blob/dev/lib/README.md#multithreading-support). You can get it working like so, from the `examples` directory: ```...

Yes, I'm a little concerned about the complexity as well. A few reasons: * Blocks are limited to 128K I think, so we'll realistically need multiple frames, each of which...

Ok, I will try that approach. I'm going on vacation soon, so maybe in 6 weeks I'll back with more :)

No, I haven't looked at this in detail yet. Let me know if you discover anything! I did add parallelism to the Go seekable-zst implementation, which is an ok option...

@tom-james-watson What would you think of the approach of allowing the user to choose an auto-paste command? That would let us wait for Wayland-based solutions to mature before building anything...

There's a few things called "pgzip" out there if I google. Which one did you have in mind?

> I have to say I _seriously_ dislike rolling our readdirnames implementation. There's a reason such things are part of the standard library. As inode numbers are expected to be...

> > But it's not documented what should happen if it returns real struct stat with zero st_ino. > > At least the linux kernel header files say the following...

Filed with Go here: https://github.com/golang/go/issues/76428

> > One better way to do this might be calling `syscall.ReadDirent` with a really large buffer size, and then using `syscall.ParseDirent` on the result. > > That will then...