I applaud this effort. I hate that we’re back to where this feels necessary. I’m not sure if there’s anything better.
JSON sure felt better than XML. But did we abstract too far, or did we just get so much better bandwidth and processors, that enriched data exploration is just insignificantly possible?
I read the use-cases for this, but I feel like: if you’ve gone so far to where this is helpful/useful, have you just gone too far?
> I read the use-cases for this, but I feel like: if you’ve gone so far to where this is helpful/useful, have you just gone too far?
I don't understand this perspective. JSON isn't used only for RPC, even if that's what most frontend software is doing. For better or worse, it became a data serialization and interchange format - the need for such support tools arises naturally once you're generating or processing anything but most trivial data, and you value your time/sanity.
Totally fair. I guess I was mostly considering the more typical client-server consumption, RPC-type uses and wasn’t really thinking just how much we use it for basic data interchange and serialization. Thanks.
I applaud this effort. I hate that we’re back to where this feels necessary. I’m not sure if there’s anything better.
JSON sure felt better than XML. But did we abstract too far, or did we just get so much better bandwidth and processors, that enriched data exploration is just insignificantly possible?
I read the use-cases for this, but I feel like: if you’ve gone so far to where this is helpful/useful, have you just gone too far?