[Defensoft3585]

Originally Posted by MrRoboSteve

One thing to think about when designing a programming language like this (whether or not you think so, you're designing a programming language) is what use cases are in and what are out.

For example, will you allow:

variables No, this is supposed to be simple.

subroutines No, this is supposed to be simple.

logic (if/then/else) No, this is supposed to be simple.

looping No, this is supposed to be simple.

Another example -- what support will you have for detecting errors in the script and communicating them to the user? If you read the code, it already has this feature.

Once you decide what is in and what is out, you should compare the effort to do what your scripting language does to the effort needed to write the same thing in the underlying language (Java, in this case). These examples will be good to use when you're trying to convince people that what you've developed makes things so much simpler that they'll learn your language in addition to Java.

My replies in bold. People seem to mistake this for an entire language - this is a data format that anyone could feasibly understand.