Couple of observations

1 - wasted too much time explaining JSON and the story behind it. Not needed. Sounded like someone who is really desperate to sell something.

2 - Did not spend too much time on alternatives. Only protobuf which YOU created/forked? So the article is about promoting the package and not about JSON.

3 - the performance difference is so insignificant that unless you are really desperately craving performance, JSON is a better alternative almost 99% of the time.

4 - congrats on your package. I understand the work that goes into creating a package but compared to JSON, it is hard to use.

5 - To become appealing as an alternative to JSON you need to handle more data types serialization and still be as easy to use while being able to serialize back and forward to JSON easily. Until then, JSON is a better alternative

6 - None of these “alternatives” are actually alternatives. They serve different purpose. JSON is hard to replace. You can only cover few scenarios here and there. JSON is amazing yet super simple.