"Javascript is ugly. That's why I made it beautiful. Ugly programming languages shouldn't have the right to exist. Don't get me wrong, Javascript is a good, stable and functional language but it's more of a personality issue conflicting with the individuality of ... what? I am exceeding the character limit for inspiring quotes? Is there such thing like a limit? 255 characters? Shut up, that's my page and my rules."
That's right. JSON and Javascript finally marged into a good-looking markup-code-thingy. Believe it or not, every function and every object on this page was created using only one JSON object. You can right-click, view the page code and see for yourself. No, honestly, you should totally do that right now because I want you to believe me.
Did you do it? Great. Let's move on.
JSONScript converts JSON objects on your webpage into valid Javascript-usable objects, functions, numbers, strings or whatever you like. Defining a parsable object is simple. Just create an array filled with objects you want the JSONScript API to parse, pass it over and you're good to go.
JSONScript.parse([
{
type : "object",
name : "myFirstJSONScriptObject"
}
])
It's that simple. JSONScript takes care of everything you shouldn't worry about. It's a solid way of shrinking down your code and making it look beautiful.
Yes. You heard me right. You, as a coder, simply need to do nothing more than give strings to the API to work with. Imagine the following. You need to have the number 123.45 stored for whatever reason. Since floats take up more space than integers, the API will first check whether the number actually needs to be represented as a float and then returns it according to the aforementioned condition. So there's indeed a difference between 123.45 and 123. The API handles it incredibly well and makes your code run faster.
JSON is beautiful and I think you know that this is a fact and not an opinion.
{$USAGE_REASON_SO_THEY_DOWNLOAD_THIS_CRAP_3}
Nothing bad will happen to your code since the eval() calls which the API requires are deeply nested in functions which can't be accessed from the outside. Hacking is almost impossible due to high security standards and we do our best in order to make the API even safer in the future.
There's a link at the top of this page. Before you do so, you should pay the documentation a visit.