While many applaud this notation superior to JSON let's face the criticsm:
It's slower than JSON, less readable than JSON and YAML, and more insecure than JSON.
To get this feature set, use YAML 2.0.
YAML supports classes and references already, and is more readable then STON.
Slower: Having to support references, STON needs to store every object in a hash. JSON doesn't need to. JSON is at least 10x faster.
Readable: JSON and YAML have much less syntax, and are more pleasant to the eye.
Insecure: Changing classes in serialization protocols without any protection is the most common exploit vector. Esp. supporting user-classes, not only builtins. YAML at least supports builtin-classes only via tags.
It's slower than JSON, less readable than JSON and YAML, and more insecure than JSON.
To get this feature set, use YAML 2.0. YAML supports classes and references already, and is more readable then STON.
Slower: Having to support references, STON needs to store every object in a hash. JSON doesn't need to. JSON is at least 10x faster.
Readable: JSON and YAML have much less syntax, and are more pleasant to the eye.
Insecure: Changing classes in serialization protocols without any protection is the most common exploit vector. Esp. supporting user-classes, not only builtins. YAML at least supports builtin-classes only via tags.