All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Critical Analysis: Why Protocol Buffers Are Poorly Designed Technology

By

b-man

8mo ago· 13 min readenOpinion

Summary

A strongly opinionated critique arguing that Protocol Buffers (protobuffers) are poorly designed, created by amateurs, and solve problems that only Google truly faces. The author contends that protobuffers are ad-hoc, filled with gotchas, difficult to compile, and that their bad design negatively impacts application code beyond just serialization layers.

Key quotes

· 4 pulled
I've spent a good deal of my professional life arguing against using protobuffers
They're clearly written by amateurs, unbelievably ad-hoc, mired in gotchas, tricky to compile
solve a problem that nobody but Google really has
the bad design of protobuffers is so persuasive that these problems manage to leak their way into your code as well
Snippet from the RSS feed
I’ve spent a good deal of my professional life arguing against using protobuffers. They’re clearly written by amateurs, unbelievably ad-hoc, mired in gotchas, tricky to compile, and solve a problem that nobody but Google really has. If these problems of p

You might also wanna read