There are some really good reasons to pick an unusual serialization protocol, and even sometimes reasons to invent your own. (Embedded systems, limited environments, licensing restrictions, etc.) Generally though, you should use something the rest of your development team / community is familiar with. Not because this is efficient in terms of resource usage on the machine, but because this is efficient in terms of teaching your other developers how your serialization protocol works.
JSON may be everywhere, and it's tempting to look at its flaws and think, "we can do better" but it also has the great benefit of having decent serialization libraries already written in the vast majority of programming languages. That's one heck of a feature.
JSON may be everywhere, and it's tempting to look at its flaws and think, "we can do better" but it also has the great benefit of having decent serialization libraries already written in the vast majority of programming languages. That's one heck of a feature.