100 hour gap between a vibecoded prototype and a working product

Re:100 hour gap between a vibecoded prototype and a working ... by andriy_koval on Sunday March 15, 2026 @02:56PM (#47390608)

> Passing data between them is off heap

how exactly you are passing data? You can pass some primitives without allocating them on heap. You can use some tiny subset of Java+standard library to write high performance code, but why would you do this instead of using Rust or C++?

[ Parent | on HN ]

Re:100 hour gap between a vibecoded prototype and a working ... by matt_heimer on Sunday March 15, 2026 @04:42PM (#47391671)

In some places I'm using https://github.com/aeron-io/agrona

Strangely this is one of the areas where I want to use project panama so I might re-implement some of the ring buffers constructs.

You allocate off heap memory and dump data into it. With modern Java classes like Arena, MemoryLayout, and VarHandle it's honestly a lot like C structs.

I answered "why" in another post in this thread.

[ Parent | on HN ]

Re:100 hour gap between a vibecoded prototype and a working ... by andriy_koval on Monday March 16, 2026 @12:13AM (#47395167)

> You allocate off heap memory and dump data into it. With modern Java classes like Arena, MemoryLayout, and VarHandle it's honestly a lot like C structs.

my opinion is that no, it is not, declaring and using C struct is 20x times more transparent, cost efficient and predictable. And that's we talking about C raw stucts, which has lots of additional ergonomics/safety/expression improvements in both c++ and rust on top of it.

[ Parent | on HN ]