This is a confusing article. Does the author know about byte alignments? Or that read/write binary values like floats is just a quick way to run into platform/p

This is a confusing article. Does the author know about byte alignments? Or that read/write binary values like floats is just a quick way to run into platform/portability issues if relevant? Or investigating how any RDBMS serializes and reads data as fast as possible? Or really any research related to the field? What about comparing spinning disk via ssd? Or even how libpng works? Or the complexity of ASN.1 notation (used for TLS certificates and many other things)? Protobuf solves a completely different problem than 'load a file from disk,' which at least FlatBuffers does. It seems like the only complaint the author has is that it doesn't work particularly at the level of abstraction they prefer. The FlatBuffers timing results also seem dubious because of the lack of profiling to say what is killing the time. Are the comparisions ruining pipelining? Why not write a transpiler to glue the protobuf output to something you actually want? It's hard to get past the first half with any confidence in methodology of testing, especially when the author leads with 'Loading things from disk is a surprisingly unsolved problem in C++.'