4 ms·
No, I'm talking about configuration files that get interpreted by code that is executing within the browser. For example, a configuration-data file format for
by derefr 13y ago
No, I'm talking about configuration files that get interpreted by code that is executing within the browser.
For example, a configuration-data file format for specifying a "brush" in a JS-client paint program. That'd obviously be a schema on top of JSON, right? Well, now you've got all of JSON's inherent limitations.
- j03w 13y agoThen you don't need JSON, all you need is the plain old JS object.
- derefr 13y agoYou're thinking of the live representation of the "model" of a brush in the program. I'm talking about the "definition" of a brush, from which the program loads that model. Another example would be, say, a "level" in an HTML5 game. These things ship alongside the game as blobs of data. Those blobs need a format that the browser can parse. Currently, JSON is that format, and it's inadequate for that.