← Back to context Comment by philwelch 8 months ago If performance isn’t an issue, why not JSON? 2 comments philwelch Reply 9rx 8 months ago Protobuf tooling isn't great, but JSON tooling is far worse. Developer experience matters too.(Technically protobuf supports JSON encoding, but its additional work to enable, again diminishing the developer experience) foobiekr 8 months ago performance is always an issue when the alternative is 2+ orders of magnitude slower.
9rx 8 months ago Protobuf tooling isn't great, but JSON tooling is far worse. Developer experience matters too.(Technically protobuf supports JSON encoding, but its additional work to enable, again diminishing the developer experience)
foobiekr 8 months ago performance is always an issue when the alternative is 2+ orders of magnitude slower.
Protobuf tooling isn't great, but JSON tooling is far worse. Developer experience matters too.
(Technically protobuf supports JSON encoding, but its additional work to enable, again diminishing the developer experience)
performance is always an issue when the alternative is 2+ orders of magnitude slower.