In Client/Server world the fact that you need to package in your frontend to be read in the backend is an obvious problem. On the hand few developers have the problem of passing code between applications. The practical cases that come to my mind just use Javascript. The crossplatform code you write for CouchDB for example is in Javascript.
You might say “well, JSON is valid JavaScript” but in practice that’s usually not relevant, as it is unsafe to eval() JSON
That’s not my experience. While you might not want to call eval() in production, it seems very useful for testing purposes to be able to copy-paste the data that you send and make an object out of it.
In 2002 when JSON was first developed and found more adoption I would expect that people used a lot of eval().
P.S. no one disagreed with my arguments at the WebAssembly CG, so don’t be too quick to judge my arguments as bad.
In this context a good argument is one that convinces people that it’s valuable to adopt something and your arguments didn’t do that.
In Client/Server world the fact that you need to package in your frontend to be read in the backend is an obvious problem. On the hand few developers have the problem of passing code between applications. The practical cases that come to my mind just use Javascript. The crossplatform code you write for CouchDB for example is in Javascript.
That’s not my experience. While you might not want to call eval() in production, it seems very useful for testing purposes to be able to copy-paste the data that you send and make an object out of it.
In 2002 when JSON was first developed and found more adoption I would expect that people used a lot of eval().
In this context a good argument is one that convinces people that it’s valuable to adopt something and your arguments didn’t do that.