Comments on: Protocol Buffers: No Big Deal

By: protocol7 » Blog Archive » RPC getting hot again?

protocol7 » Blog Archive » RPC getting hot again? — Thu, 31 Jul 2008 18:56:02 +0000

[...] much quite. But, as with anything touched by todays Midas, Google’s Protocol buffers stirred a bigger debate on the merits of [...]

By: WSOAC#24 - Protocol Buffers? RPC? are we going back in time? - Service Endpoint

WSOAC#24 - Protocol Buffers? RPC? are we going back in time? - Service Endpoint — Wed, 16 Jul 2008 21:25:53 +0000

[...] Vinoski – Protocol Buffers: No Big Deal, Protocol Buffers: Leaky [...]

By: Protocol Buffers – Missing Usage Guide? « Libor.SOUCEK(”WEBLog”)

Mon, 14 Jul 2008 16:57:17 +0000

[...] call. Among posts on this topic were such highly respectable people like Ted Neward, Stefan Tilkov, Steve Vinosky here and here or Dare Obasanjo. Unfortunately those “big shooters” failed short with clean [...]

By: badger

badger — Mon, 14 Jul 2008 14:21:43 +0000

Google is the new Microsoft — inventing something new for a problem that is known for decades and already has several widely used, well known industry standard solutions like ASN.1. The saddest of all is that the google guy announcing the opening of the PB source doesn’t even know about ASN.1:

“Sorry, I personally am not very familiar with ASN.1 DER. A brief look at some documentation suggests to me that it is more complicated than Protocol Buffers, which can be good or bad depending on whether you need that complication.”

By: Anthony Tarlano

Anthony Tarlano — Sat, 12 Jul 2008 22:13:27 +0000

It's beginning to look as if Google is becoming something of a sourceforge even for their own external releases. Last month it was App Engine with YAML is a human friendly data serialization, this week it's lets go binary with Protocol Buffers.. From the outside it looks as if Google is suffering from a bit of "cat herding syndrome".. Maybe this blog post from a couple weeks ago wasn't so far off Tony