Re:Bebop v3: a fast, modern replacement for Protocol Buffers
by flohofwoe on Tuesday March 12, 2024 @01:00PM
(#39681924)
Not sure if it has improved in the last few years or if other target languages are better, but the protobuf code generation for C++ was pretty much the worst C++ code in terms of bloat I have ever seen. And I've seen a lot of bad C++ code ;)
[ Parent
| on HN ]
Re:Bebop v3: a fast, modern replacement for Protocol Buffers
by martinky24 on Tuesday March 12, 2024 @01:20PM
(#39682177)
In what ways did that meaningfully matter though? I use generated C++ protobuf code, and the API is clean even if the implementation looks like it wasn't hand written? If you think the C++ code is bad, you should see the Python... But again, the APIs are clean and robust so it hasn't affected me.
Re:Bebop v3: a fast, modern replacement for Protocol Buffers
by mst on Tuesday March 12, 2024 @01:44PM
(#39682499)
The "bloat" part is probably going to impact your compile times.
Also I tend to want generated code to be at least ish comprehensible in case I need to debug into it - from what you're saying, everything has gone sufficiently well in terms of 'clean and robust' that that hasn't been an issue for you in practice ... but justified or not, it's going to worry me anyway.