![]() ![]() ![]() For Square, these omitted features all have reasonable alternatives, and the advantage of having those features was outweighed by the cost they impose on the clarity of the API. Wire does omit a few protocol buffer features in order to create a simple, intuitive, idiomatic API. Since Wire isn’t the official compiler we’ve been able to simplify the feature set some, thus allowing us to streamline the output, all while staying compatible with the protocol buffer wire format. As our organization and codebase scaled, however, Wire also became the tool we used to help protos scale with us. It was also an opportunity to create proto APIs that felt more idiomatic. #ISWIFT APP ANDROID#So if there’s an official proto compiler, why build a new one? The original reason for writing the Java version of Wire was technical: Android binaries are limited in the number of methods they can have, and the official protoc output had a lot of methods, many of which were only in support of features that we considered unnecessary and confusing (and which, for the most part, Google ended up removing in Proto3). For Swift, the official plugin is primarily maintained by Apple. proto files for many languages, each of which is implemented as a plugin to the compiler. The protoc compiler can generate code from. Why Wire?Īlong with the specification, Google maintains an official compiler for the protocol buffer format: protoc. The format was created by Google and they provide excellent documentation with more information. Protocol buffers are a powerful and efficient way to transfer data between devices. Wire already supports compiling your protocol buffer files into Java and Kotlin, and today Swift joins that family. We’re excited to announce support for Swift in Wire. Eric Firestone and Jake Wharton on AugIntroduction ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |