4 ms·
"you’d expect it to do something pretty deep right?... Nope. It reads in a string and writes out a string." We're all just doing the same thing in one way or a
by sudo_bang_bang 11y ago
"you’d expect it to do something pretty deep right?... Nope. It reads in a string and writes out a string."
We're all just doing the same thing in one way or another :) Good work and nice article.
- aiiane 11y agoAlong these lines, we have a joke at Google that all of our problems are just transforming one protocol buffer into another.
- feelix 11y agoAnd programming anything, or taking over the universe for that matter, is just a matter of the hitting the right keys on the keyboard in the right order.
- sudo_bang_bang 11y ago"Protocol buffers are a language-neutral, platform-neutral extensible mechanism for serializing structured data." [1] Interesting, I figured Google was handling data serialization in their own way, and now I know[2] [1]https://developers.google.com/protocol-buffers/docs/overview https://developers.google.com/protocol-buffers/docs/overview [2]https://github.com/google/protobuf https://github.com/google/protobuf
- QuercusMax 11y agoIt's so true... I've only been at Google since the end of June and already have written a few proto converters. And teaching the super-newbies (i.e. fresh out of school) the difference between the frontend and backend protobufs...
- ridiculous_fish 11y agoFor what it's worth, I never encountered protobufs during my time at Google.
- Dylan16807 11y agoRight, cute, but you're cutting out the context that it's outputting the same thing as the input.
- gsnedders 11y agoThis is my mostly terrible argument when people start claiming compilers are hard. :)