3 ms·
Coming from protobuf land, this tool seems gross. It's XML schema all over again. Why are we trying to shoehorn a schema design language into a format that isn
by echelon 8y ago
Coming from protobuf land, this tool seems gross. It's XML schema all over again.
Why are we trying to shoehorn a schema design language into a format that isn't good for human authoring? It's annoying to write JSON, yet the language masquerades as being human-readable.
Frontend engineers should check out protobuf. It's an amazing data definition language that generates bindings in every language under the sun and has a compact binary serialization that is much more efficient than JSON both to encode/decode and transmit over the wire.
JSON should die the same death XML did. It's so bad.
- cageface 8y agoBeing able to see JSON responses in browser dev tools is extremely helpful for development and debugging. Is there something similar for protobuf?
- carlmr 8y agoI concur, JSON is easy enough to read/write for humans, easier to parse than XML, too, it kind of hits the sweet spot in between protobuf and XML.
- hasperdi 8y agoProtobuf is a lower level interface. You can't rely on it for validation and use it for complex model / schema. For example oneof customer (individual / organisation) with different distinct fields. In protobuf, all these fields need to be defined.