This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:google:protobuf [2019/05/23 15:54] nick created |
dido:public:ra:xapend:xapend.b_stds:defact:google:protobuf [2021/11/09 15:41] (current) char ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======== Protocol Buffers ======== | + | ===== Google: Protocol Buffers ===== |
| - | [[dido:public:stds:defact| return to the de facto Standards bodies ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:google:start| return to Google page ]] |
| **Source: [[https://developers.google.com/protocol-buffers/ | The following is from Google ''Protocol Buffers '' site ]]** | **Source: [[https://developers.google.com/protocol-buffers/ | The following is from Google ''Protocol Buffers '' site ]]** | ||
| - | : //Protocol buffers are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data – think XML, but smaller, faster, and simpler. You define how you want your data to be structured once, then you can use special generated source code to easily write and read your structured data to and from a variety of data streams and using a variety of languages.// | + | : //Protocol buffers are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data – think XML, but smaller, faster, and simpler. You define how you want your data to be structured once, then you can use special generated [[dido:public:ra:xapend:xapend.a_glossary:s:sourcecode|source code]] to easily write and read your structured data to and from a variety of data streams and using a variety of languages.// |
| <table> | <table> | ||
| - | <caption>Data Sheet for Protocol Buffers. | + | <caption>Data Sheet for Protocol Buffers |
| </caption> | </caption> | ||
| ^ Characteristic ^ Value ^ | ^ Characteristic ^ Value ^ | ||
| - | | Paradigm | Multi-paradigm: concurrent, functional,(( | + | | Developer | Google | |
| - | "First-Class Functions in Go". Retrieved November 14, 2018. Go supports ... a functional programming style in a strongly typed language. | + | | Initial release | 10 November 2009(( |
| - | )) imperative, object-oriented (( | + | "Frequently Asked Questions | Protocol Buffers". Google Developers. Retrieved 2 October 2016. |
| - | Is Go an object-oriented language?". Retrieved April 13, 2019. Although Go has types and methods and allows an object-oriented style of programming, there is no type hierarchy. | + | )) | |
| - | ))(( | + | | Stable release | 3.7.1 / March 26, 2019(( |
| - | "Go: code that grows with grace". Retrieved June 24, 2018. Go is Object Oriented, but not in the usual way. | + | "Releases - google/protobuf". Retrieved 2 April 2019 – via GitHub. |
| - | )) | | + | )) | |
| - | | Typing | Inferred, static, strong, structural(( | + | | Repository | [[https://github.com/protocolbuffers/protobuf]] | |
| - | "Why doesn't Go have "implements" declarations?". golang.org. Retrieved October 1, 2015. | + | |
| - | ))(( | + | |
| - | Pike, Rob (December 22, 2014). "Rob Pike on Twitter". Retrieved March 13, 2016. Go has structural typing, not duck typing. Full interface satisfaction is checked and required. | + | |
| - | )) | | + | |
| - | | Original author(s) | Robert Griesemer, Rob Pike, Ken Thompson | | + | |
| - | | Developer | The Go Authors(( | + | |
| - | Text file LICENSE". The Go Programming Language. Google. Retrieved October 5, 2012. | + | |
| - | )) | | + | |
| - | | Initial release | 10 November 2009 | | + | |
| - | | Stable release | 1.12.5 / May 6, 2019;(( | + | |
| - | "Release History - The Go Programming Language". Retrieved April 19, 2019. | + | |
| - | )) | | + | |
| - | | Repository | git.kernel.org/pub/scm/git/git.git/ | | + | |
| | Written in | Go, assembly language (gc); C++ (gccgo) | | | Written in | Go, assembly language (gc); C++ (gccgo) | | ||
| - | | Operating system | DragonFly BSD, FreeBSD, Linux, macOS, NetBSD, OpenBSD,(( | + | | Operating system | Any | |
| - | "lang/go: go-1.4 – Go programming language". OpenBSD ports. December 23, 2014. Retrieved January 19, 2015. | + | |
| - | )) Plan 9,(( | + | |
| - | "Go Porting Efforts". Go Language Resources. cat-v. January 12, 2010. Retrieved January 18, 2010. | + | |
| - | )) Solaris, Windows | | + | |
| | Available in | English | | | Available in | English | | ||
| | Type | Version control | | | Type | Version control | | ||
| - | | License | BSD-style(( | + | | License | BSD | |
| - | Text file LICENSE". The Go Programming Language. Google. Retrieved October 5, 2012. | + | | Website | [[https://developers.google.com/protocol-buffers/]] | |
| - | )) + patent grant(( | + | |
| - | Additional IP Rights Grant". The Go Programming Language. Google. Retrieved October 5, 2012. | + | |
| - | )) | | + | |
| - | | Website | https://golang.org/ | | + | |
| </table> | </table> | ||
| + | |||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||