Vicent Martí

Hey @nockty, thanks for reaching out. You actually caught me off on paternity leave, which is the reason why the repository was basically frozen for the better part of this...

Hey! I've reached out to PlanetScale's legal team and we're ironing out the last kinks. My goal is to add @nockty as a committer to this repository some day this...

As a hint for people interesting on contributing to the library: I think the main open issue right now blocking our next release is (de)serialization support for well-known types. There's...

@nockty: :wave: welcome back from your holidays! I've given you triage access to the repository. Thanks again for your interest on the project and let me know what can I...

Cool! First off, thanks @jzelinskie for taking the time to contribute and review this with us. @mattrobenolt's concern is certainly valid, but as you've already pointed out, the pattern we...

Now testing https://github.com/vitessio/vitess/pull/16790 in Vitess itself. Hoping this will show up in the benchmarks!

This has worked wonderfully in upstream Vitess: https://github.com/vitessio/vitess/pull/16790#issuecomment-2419021276

@francoposa: What are you exactly looking for in a release? As explained earlier, we're not looking to merge the custom GRPC codec because that'd introduce a GRPC dependency on the...

I'm not opposed to merging this, but I'm not quite sure of the rationale. Usually when you're already working with `jsonpb`, performance is no longer a priority, so I don't...

Nope, not at all. I don't own any ARM CPUs. Vitess isn't tested on ARM on CI either. Running ARM Vitess in production seems like a risky proposition at this...