For the last week or so I started designing a simple scripting language that will serve as a base for my new product. The product code name is “Scheduled Jobs” and its main purpose will be to automate Windows jobs as backup of files and databases, various simple and not so simple tasks, etc. At first I thought it would be enough to define the tasks that will be executed in a job in XML file format, but after thoroughly examining the problematic it become obvious this approach will have many weaknesses and at the end, probably it wouldn’t be possible to support more complex tasks.
Then I started exploring different scripts that supports embedding in third party applications, specifically I took a look at Lua, Perl and Javascript. I really liked the Perl syntax and even spent some time on it, compiling it and running few simple scripts. But, again it become obvious I’ll just waste my time with these options as my main aim was full control over the underlying structure and endless flexibility.
That’s when I decided to design my own scripting language. It must be deadly simple to use, with as less rules as possible, with a big library that will provide most of the functionality.
So, at least I have a name for it: Moscripto. The idea for the name came to me from the name of the tiny insect Mosquito, which I believe this script language will be: tiny.