zpp_bits
FlatBuffers
zpp_bits | FlatBuffers | |
---|---|---|
9 | 48 | |
658 | 22,048 | |
- | 0.5% | |
4.9 | 8.7 | |
about 1 month ago | 9 days ago | |
C++ | C++ | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zpp_bits
-
How to arrange a bunch of variables into one array of bytes in memory?
I would either look at https://github.com/eyalz800/zpp_bits or https://github.com/stephenberry/glaze. FYI, glaze both supports json and binary.
-
Delimiting a Binary File/ Parsing a Binary File
For something bigger or more complicated I'd recommend something like google's protobuf library or https://github.com/eyalz800/zpp_bits if you're able to use external dependencies.
-
alpaca: A new serialization library written in C++17 - Pack C++ structs into a compact byte-array without any macros or boilerplate
Can you give us some hint on what would be different in your project from the libraries that do roughly the same? The tser author has made a comment here, but I know that cista and zpp_bits probably have some overlap with alpaca. I just don't have a specific use case now, so I don't have an urge to dive deep into the topic, but in the past I've needed a library like yours, and right now I would have to evaluate half a dozen libraries to know would be "best" or more appropriate.
-
Yet another serializer. Serialize C/C++ datatypes, POD and classes, store or retrieve data to and from ostream and istream objects. With support for streams save or read data with files and send or receive them over networks. Its lightweight and header-only.
It might be interesting for you to compare with https://github.com/eyalz800/zpp_bits
-
Automatic Serialization in C++ for Game Engines | IndieGameDev
How about this https://github.com/eyalz800/zpp_bits
- Next step in zpp::bits serialization - protobuf without code generation - no proto file required- (experimental)
- Just added cool RPC capabilities for my C++20 serialization (zpp_bits)
-
Brand new C++20 serialization library (one header)
Since C++20 I felt I could improve my previous serialization library, and to avoid the complexity of supporting multiple C++ standard I decided to create a new one zpp_bits
FlatBuffers
- FlatBuffers – an efficient cross platform serialization library for many langs
-
Cap'n Proto 1.0
I don't work at Cloudflare but follow their work and occasionally work on performance sensitive projects.
If I had to guess, they looked at the landscape a bit like I do and regarded Cap'n Proto, flatbuffers, SBE, etc. as being in one category apart from other data formats like Avro, protobuf, and the like.
So once you're committed to record'ish shaped (rather than columnar like Parquet) data that has an upfront parse time of zero (nominally, there could be marshalling if you transmogrify the field values on read), the list gets pretty short.
https://capnproto.org/news/2014-06-17-capnproto-flatbuffers-... goes into some of the trade-offs here.
Cap'n Proto was originally made for https://sandstorm.io/. That work (which Kenton has presumably done at Cloudflare since he's been employed there) eventually turned into Cloudflare workers.
Another consideration: https://github.com/google/flatbuffers/issues/2#issuecomment-...
-
Anyone has experience with reverse engineering flatbuffers?
Much more in the discussion of this particular issue onGitHub: flatbuffers:Reverse engineering #4258
-
Flatty - flat message buffers with direct mapping to Rust types without packing/unpacking
Related but not Rust-specific: FlatBuffers, Cap'n Proto.
- flatbuffers - FlatBuffers: Memory Efficient Serialization Library
-
How do AAA studios make update-compatible save systems?
If json files are a concern because of space, you can always look into something like protobuffers or flatbuffers. But whatever you use, you should try to find a solution where you don't have to think about the actual serialization/deserialization of your objects, and can just concentrate on the data.
- QuickBuffers 1.1 released
-
Choosing a protocol for communication between multiple microcontrollers
Or, as an alternative to protobuffers, there's also flatbuffers, which is lighter weight and needs less memory: https://google.github.io/flatbuffers/
- FlatBuffers: FlatBuffers
-
Is using Flatbuffers to parse sensor data a bad application of Flatbuffers?
As the title suggests, I am considering using Flatbuffers as a way to parse sensor data that has been stored in local datafiles. The project language is python.
What are some alternatives?
serializer - A single header standard C++ serialization framework.
Protobuf - Protocol Buffers - Google's data interchange format
serializer - Yet another serialzer
MessagePack - MessagePack implementation for C and C++ / msgpack.org[C/C++]
libnop - libnop: C++ Native Object Protocols
MessagePack - MessagePack serializer implementation for Java / msgpack.org[Java]
MoreThanTuple - C++20 library for binary serialization of arbitrary aggregates or tuples. The library also unifies work with tuples and aggregates
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library
alpaca - Serialization library written in C++17 - Pack C++ structs into a compact byte-array without any macros or boilerplate code
cereal - A C++11 library for serialization
glaze - Extremely fast, in memory, JSON and interface library for modern C++
Kryo - Java binary serialization and cloning: fast, efficient, automatic