11–20 of 59 posts
The only thing that says is schemeless and is zero copy is Apache Fory which is missing from the benchmark.
This looks like most of it was vibecoded. Unnecessary comments like: clientChannel.configureBlocking(false); // Non-blocking client can be found throughout the source, and the project's landing page is a good example of typical SOTA models' outputs when asked for a frontend landing page.
It's not a local IPC exactly. The roundtrip benchmark stat is for a TCP server-client ping/pong call using a 2 KB payload; TCP is although on local loopback (127.0.0.1). The payload is encoded using myra-codec FFM MemorySegment directly into a pre-registered buffer in io_uring SQE on the server. Similarly, on the client side CQE writes encoded payload directly into a client provided MemorySegment. The whole process s…
There's WAY too much content, way too many names and stuff that feels subtly off. I'm 37, been on this site for 16 years. I'm assuming target audience here is enterprise Java developers, which isn't my home, so I'm sure I'm missing some stuff is idiomatic in that culture.
But the vast, vast amount of things that are completely unfamiliar tells me something else is going on and it's not good.
Like I bet this is f'ing cool, otherwise you wouldn't put in the effort to share it. But you're better off having something super brief** in a GitHub README than a pseudo-marketing site that's straining to fit a cool technical thing into the wrong template.
* https://news.ycombinator.com/item?id=46255661
** what you wrote is great! "The payload is encoded using myra-codec FFM MemorySegment directly into a pre-registered buffer in io_uring SQE on the server. Similarly, on the client side CQE writes encoded payload directly into a client provided MemorySegment. The whole process saves a few SYSCALLs. Also, the above process is zero copy." -- then the site looks like it wants to sell N different products and confusing flowcharts, but really, you're just geeked out and did something cool and want to share the technical details. So it's designed for the wrong audience.
This looks like most of it was vibecoded. Unnecessary comments like: clientChannel.configureBlocking(false); // Non-blocking client can be found throughout the source, and the project's landing page is a good example of typical SOTA models' outputs when asked for a frontend landing page.
This looks like most of it was vibecoded. Unnecessary comments like: clientChannel.configureBlocking(false); // Non-blocking client can be found throughout the source, and the project's landing page is a good example of typical SOTA models' outputs when asked for a frontend landing page.
Okay, but is that a bad thing?
This looks like most of it was vibecoded. Unnecessary comments like: clientChannel.configureBlocking(false); // Non-blocking client can be found throughout the source, and the project's landing page is a good example of typical SOTA models' outputs when asked for a frontend landing page.
Okay, but is that a bad thing?
Earlier quoted context omitted.
Okay, but is that a bad thing?
For your pet project? No. For something you're building for others to use? Almost certainly yes.
Earlier quoted context omitted.
Okay, but is that a bad thing?
If the author doesn't understand their own code, I probably won't
27us roundtrip is not really state of the art for zero copy IPC, about 1us would be. What is causing this overhead?
Earlier quoted context omitted.
If the author doesn't understand their own code, I probably won't
Vibe coding doesnt mean the author doesnt understand their code. Its likely that they don't want carpal tunnel from typing out trivial code and hence offload that labor to a machine.