This is a problem. The generated message classes and serialisation code are about 10 years out of date.
This is a problem. The generated message classes and serialisation code are about 10 years out of date.
@markrendle I protest to some extent - @JamesNK and others have definitely done some work in this area. But compatibility requirements make it hard to go *too* far without making breaking changes which would be really, really painful.
@jonskeet @markrendle @JamesNK Yep, but I would honestly love a non protoc code generator for C#. All source generators without having to bring the existing toolchain and baggage along
@davidfowl @jonskeet @markrendle @JamesNK I've spiked this about 3 times but never had the time to finish something. I have, separately: - a spike of a whole new optimized reader/writer layer - a spike of a full generator Roslyn impl - full schema tools for .proto, 10% managed Maybe we could fund the time to finish :)
@marcgravell @jonskeet @markrendle @JamesNK Microsoft should fund it. We use grpc internally too. There's lots of interest in making it faster. The current implementation is fine but there's lots of performance being left on the table for the sake for backwards compat. I was waiting for @neuecc to fix it 😁
@davidfowl @marcgravell @jonskeet @markrendle @JamesNK @neuecc Also nullable types that don't suck with it. And records. And preferably readonly record structs for DTOs. (or at least the option to use them) And fix the pathing issues so multi project solutions don't suck.
@davidfowl @jonskeet @markrendle @JamesNK @neuecc If only I was on the "distributed systems" team. OH WAIT A DAMNED MINUTE!