3 ms·
Personally, I don't see a huge upsell over JSON for interop. Typing is great, but largely mitigated by things like typescript, graphql generators etc etc. edit:
by MisterKent 2y ago
Personally, I don't see a huge upsell over JSON for interop. Typing is great, but largely mitigated by things like typescript, graphql generators etc etc. edit: and json schema
The biggest issue I see with JSON today is the inability to self reference values. Data duplication overhead is high, and deserializing doesn't work as expected if you want two objects to be reference equal.
Also, nitpick: that syntax would be a grind to write manually vs JSON.
- paulmooreparks 2y agoThanks so much for your input. Yeah, it's a bit more work to type, but I've already gotten a bit faster (even though I change the syntax so much). Copilot has been helpful, too, once it learned what I was trying to do. A proper syntax helper for VS Code and Visual Studio would probably make things a lot easier, too. I haven't thought about self-reference. I'll pin that to the list of things to play with. For me, it was comments, placeholders, and typing, and those drove the syntax evolution, especially with regard to nesting of elements. Trust me, you would have really hated the first couple of iterations.