Google Protocol Buffers
submitted 1 year ago by [deleted] from (en.wikipedia.org)
[–]fschmidt 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 0 fun3 insightful - 1 fun - 1 year ago* (4 children)
What is the point? Throughput is high. REST is bad for complex network communication because it requires multiple connections. But for the data format, JSON is just fine.
[–][deleted] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 0 fun2 insightful - 1 fun - 1 year ago (3 children)
The point is the interoperability. Big cross platform potential. I always had a thing for POSIX compliance, this scratches a similar itch, although it's not so impressive on the technical merits.
[–]fschmidt 3 insightful - 1 fun3 insightful - 0 fun4 insightful - 0 fun4 insightful - 1 fun - 1 year ago (2 children)
Interoperability depends on standards, and standards must be simple to work. Everything that Google does is overcomplicated because they are modern scum, so they cannot produce any reasonable standards.
[–][deleted] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 0 fun2 insightful - 1 fun - 1 year ago (1 child)
I will be the first to adopt the FSchmidt Standard Interoperability Model, but we got what we got unfortunately.
[–]fschmidt 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 0 fun3 insightful - 1 fun - 1 year ago (0 children)
My model is goodjava.rpc. But don't adopt it because it won't be standard. Instead join my Reactionary Software movement.
[–]SoCo 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 0 fun2 insightful - 1 fun - 1 year ago (0 children)
These are getting used everywhere. Seems like an overthinking of communications in many applications of it.
use the following search parameters to narrow your results:
e.g. sub:pics site:imgur.com dog
sub:pics site:imgur.com dog
advanced search: by author, sub...
~5 users here now
Links:
[–]fschmidt 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 0 fun3 insightful - 1 fun - (4 children)
[–][deleted] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 0 fun2 insightful - 1 fun - (3 children)
[–]fschmidt 3 insightful - 1 fun3 insightful - 0 fun4 insightful - 0 fun4 insightful - 1 fun - (2 children)
[–][deleted] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 0 fun2 insightful - 1 fun - (1 child)
[–]fschmidt 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 0 fun3 insightful - 1 fun - (0 children)
[–]SoCo 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 0 fun2 insightful - 1 fun - (0 children)