nviennot

After trying to like rkyv, I came to the conclusion that the serialization/deserializarion API is not ergonomic due to the heavy use of generics in their API.

I think we can do better.

This landing page is terrible.

There's a bunch of professional photos of the camera, two with a hand, then two next to a pair of pants, then on a handbag.

Only after all that it is shown on a laptop, where it is actually used! It should be the first image. Also, there's so little comparison between built-in webcam image and their offerings.

Then there's a huge video with a bead sliding on the rope holding the camera. It seems that the marketers are just masturbating with the high-quality photography they made. It's not actually useful.

This is not a problem users were like "I don't know how I can go from a meeting to another with my camera".

Also, their "Have you ever wished you could instantly mute yourself in a video call without having to look for that elusive mic button? Well, now you can have it." -- this is a solved problem with mute buttons on F1/F2 or whatever your laptop does. Or at least, current mute solutions are not harder than "I'm bring my own webcam, plug it in, configure the audio source, position it correctly on the top of my screen"

This landing page is out-of-touch with actual problems users may have.

Added, thanks

So what did you do to get the most performance out of the system? pin the threads to specific CPUs?

It would be nice to have another bench from the Alder Lake, so we can validate the results

The data seems problematic, there's a few 0's here and there and some strange noise in the rest. Increase the number of samples / iterations with `core-to-core-latency 30000 1000 --csv > output.csv`

Okay, I've added a file

Very nice

It'd be great if you could provide the output.csv actually :D

I think there's a CLI tool for pastebin