we _unfortunately_ gravitated towards protobuf's despite my fervent appeal to go with capn-proto. that has caused a cascade of troubles / missed opportunities for optimizations etc. etc.
I don't like that protobuf has recently started linking with abseil, which despite being a good framework, I can't use it if it doesn't build absolutely everywhere I need it to. So, maybe I'll be forced over to CapnProto one of these days?
If MinGW isn't already supported, if probably expect to have to take that over yourself.
What troubles has protobuf caused you?
we are primarily a c++ shop, so all comments are from that vantage point. in no particular order following:
1. extremely bloated generated code.
2. wire format is not optimal, specifically for large nested messages which trashes the cache on a already severely constrained h/w.
3. not easy to perform shared-memory exchange for large messages, for example, if you have 'string' types in your messages, those cannot be allocated on arenas.
4. <this space is for rent>