update docs

Author: maihd

Json.h

@@ -85,7 +85,8 @@ typedef struct JsonObjectMember JsonObjectMember;
 
 struct Json
 {
-    JsonType                type;       // Type of value: number, boolean, string, array, object
+    JsonType                type;   // Type of value: number, boolean, string, array, object
+    // int32_t                 next : 24;  // Next item in array, object 
     int32_t                 length;     // Length of value, always 1 on primitive types, UTF8 string length
     union
     {
@@ -106,6 +107,12 @@ struct JsonObjectMember
     Json                    value;
 };
 
+#if 0
+#include <assert.h>
+static_assert(sizeof(Json) == 16, "");
+static_assert(alignof(Json) == 16, "");
+#endif
+
 // -------------------------------------------------------------------
 // Constants
 // -------------------------------------------------------------------

README.md

@@ -46,7 +46,10 @@ After sometimes use this, I found that API have flaws of its own:
 - Continue to the above, reorder should help? Not exactly, how to reorder, how much reorder overhead, that too much works for simple parsing simple data format like JSON.
 - No big projects usage.
 - Parsing still too complex
--> Decisioning to exploring some best practices from other parser, [MetaDesk](https://github.com/ryanfleury/metadesk) is good example. Linked list in one single arena of memory is good enough.
+> _*Conclusion*_: 
+> - Decisioning to exploring some best practices from other parser, [MetaDesk](https://github.com/ryanfleury/metadesk) is good example. Linked list in one single arena of memory is good enough.
+> - For production code, we should use battle-tested library. Mai suggestion is [yyjson](https://github.com/ibireme/yyjson)
+> - Start new project call sjson (Simplified Json, but also mean Simplified Json Parser, more simple implementation)
 
 
 ## Examples