This is one of those “demo” that no serious people will use it, no other people will want to improve it ( because I can also use ai to generate one myself). It is just useful to show how “good” it is.

“C includes show it age.” But C++ is stating not because of there is a “++” there but because of there is a “C”.

Decades–old parts of the ++ also contribute.

As someone worked in AWS, I will laughing at some one who really believes that s3 is “bottomless”.

Also there seems not much use cases nowadays want this, if there are any, they already use Kafka.

> laughing at some one who really believes that s3 is “bottomless”.

Please elaborate on this.

You replace protobuff with a different protocol which is implemented in rust. You can not replace your food with a soap.

Again this is benefiting wealthy people has a large amount of capital instead of workers.

People are at same time complaining about data slow but they seem to happily paying AWS 10x for less iops and bandwidth.

What does this have to do with consumer SATA SSDs?

This is not an area an open source will work. Particularly your main target is on cloud customers.

If you are confident with your work, you should not open your source because that’s the single leverage you have.

In the real world, unless are writing a very specialized system, intended to run only on Linux 6.0 and never, it just is not realistic and you will need some sort of abstraction layer to support at the very least additionally poll to be portable across all POSIX and POSIX like systems. Then if you want your thing to also run on Windows, IOCP rides in too...

I used 6.0 because 5.8-5.9 is roughly when io_uring became interesting to use for most use cases with zero copies, prepared buffers and other goodies, and 6.0 is roughly when people finally started being able to craft benchmarks where io_uring implementations beat epoll.

Some people would rather have an abstraction over io_uring and kqueue rather than choosing a single API that works everywhere they want to run, choosing to only run on the OS that provides the API they prefer, or writing their loop (and anything else) for all the APIs they want to support.

But I agree with you; I'd rather use the thing without excess abstraction, and the standard apis work well enough for most applications. Some things do make sense to do the work to increase performance though.

I do both: charge people to do it for them and do it for myself.

(your second sentence is a bit confusing)

Workers is a very expensive computing facility. Yeah, it is cheaper than AWS lambda but people don’t use that for everything.