protox 1.0.0 has been released! As no new features have been added and the API has been stable for a long time, I thought it was finally the time to mark it stable.

So, as a recall: why would you want to use protox rather than the others libraries like protobuf-elixir which has more features (and users )? Well, It really depends on how much do you need a reliable implementation. As protox has been written for the case of autonomous vehicles, reliability was more important than features. Thus, it has been has been thoroughly tested using the conformance checker provided by Google, has a 100% test coverage and uses property based testing.

Don’t hesitate to give it a try .

protox 1.2.1 is now available!
The main changes since 1.0.0 are:

• generation of one file per module, which speeds up the compilation if you have a lot of protobuf messages
• possibility to ignore unknown fields

And of course, it’s still 100% compliant with the Google conformance checker .

protox 2.0 is out!

What it brings:

• encoding speed boost of around 50%
• significant internal restructuring for easier maintenance
• consistent way of accessing a message’s schema

Being a major release, there are breaking changes:

• drop support of JSON encoding/decoding (the implementation was half-baked and even Google doesn’t recommend using the JSON encoding). I hope people won’t be disappointed by this, but looking at the projects that use protox, none of them are relying on this functionality.
• encoding functions now return the size of the encoded data so you don’t need to compute it yourself (which, by the way, provided the encoding speedup)
• many generated functions to get a message schema information (like the syntax) are removed and the corresponding information are available in the structure returned by schema/0.

The complete changelog.