let's talk about flatbuffersI think they're neat and underutilized
>>109604885I literally wrote this for C++ two decades ago.Still using it till this day in C# and Nim.And honestly, I think 90% of all developers did the same at some point.Google just trying to stay relevant in 2026, nothing more nothing less.
>>109604885never used thisas far as i know its just a codegenerator basicallybut i prefer hand crafting my parser thank you.
>>109604885explain for the retards
>>109604885it's a really interesting trade-off. You get fast zero-copy reads at the expense of slower writes and bloated network packets compared to other serialization formats like Protobuf. If I'm writing a networked app, though, I generally prioritize smaller packets so I'm not sure I'd ever reach for FlatBuffers
>>109605073int abc = (int*)bytesThat's literally the whole magic.
>>109605073it's like json but less gay
>>109604885You're not Google.Every API you ever develop fares better with JSON. Every client can easily read it, every developer can understand it, everyone can easily debug it in the tools they know.Modern SIMD JSON libraries can parse gigabytes of JSON a second.The boring solution is usually the better one. When I was a young developer, I also wanted to use all the new, shiny stuff I read about. It was a mistake.
>>109605154I'm not gonna use json for inter-process communication
>>109605128c devs have been doing this for years thoughever?
>>109604885It's cool that a format similar to Cap'n Proto is somewhat adopted. They seem to be focussing on Cap'n Web nowadays (a format for the web using json)
