|
|
|
|
|
|
by peternicky
2473 days ago
|
|
|
What are the core problems that stem from json usage? I’m all for challenging status quo but from my little experience, I wasn’t aware json was THAT problematic that we need to consider an alternative as drastically different as this project is. Would love to here the problems that spurred this project. |
|
|
- Won't it be good if you exchange less amount of data?
- Won't it be good if serializer/deserializer validates the data before processing/loading/serializing, and you don't have to write special validation code?
- Won't it be good if you only pass, data and not the definitions over the wire? For example just send "Spiderman, 25" instead of { "name": "Spiderman", "age", 25 }
- Won't it be good if you do not mix, data and metadata (such as recordCount, nextPage, etc...)?
- Won't it be good if the object collection can be streamed through partial serialization?
Internet Object improves on all these front!