Like basically we want to establish a strict word boundary for a transmission between two entities. They can be a Frontend talking to a Backend or consuming a REST API. The mere fact that JSON has no native guardrails around the amount that can be sent, it is impossible to backport JSON for the cost is huge, so we go one step further in the realm of OSI model and picked a place. Presentation. Layer 6. Protocol. Morse/36.
Morse/36
Imagine getting a patient record from a remote hospitals network in just 36-characters.
Imagine 2 fire drones talking with each other telling that they are out of gas and heading for refueling through a 36-character packet.
Because while it is excellent, JSON is unnecessarily bloated. But we can not ask the industry to move away from JSON or prior to Morse/36 standards, but we are aiming to create a Presentation layer protocol ultimately. The sixth layer in OSI model.
