From a2b0bcdf1367aafcb9b4326402a6b5720dc55268 Mon Sep 17 00:00:00 2001 From: Wouter van Oortmerssen Date: Fri, 21 May 2021 09:56:35 -0700 Subject: [PATCH] Updated Why FlatBuffers vs other options? (markdown) --- Why-FlatBuffers-vs-other-options?.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Why-FlatBuffers-vs-other-options?.md b/Why-FlatBuffers-vs-other-options?.md index e84b99d..dcae021 100644 --- a/Why-FlatBuffers-vs-other-options?.md +++ b/Why-FlatBuffers-vs-other-options?.md @@ -11,4 +11,4 @@ This is a long topic, but one thing to highlight is the _range_ of possible use -----json------ | ``` -Meaning even if you don't need to be particularly fast or flexible with your current use-case, FlatBuffers scales in every direction, with more representation choices than any other serialization system, and more API choices (use with JSON, use with object API etc) \ No newline at end of file +Meaning even if you don't need to be particularly fast or flexible with your current use-case, FlatBuffers scales in every direction, with more representation choices than any other serialization system, and more API choices (use with JSON, use with object API etc), and easy ways for the first 3 options to work together (struct/table/flex). \ No newline at end of file