CSTN VS gaiman

My recommendation is to just write something, even if it sucks. That goes for any concept. You'll learn faster and better by interacting with the machinery yourself versus trying to interpret someone else's abstract understanding of the machinery. In this case, that means choose a simple language or write your own grammar to play with, and make a parser for it. The first real parser I made is a recursive descent parser that parses a relative of JSON. If you're curious, my code is available), but I was a lesser programmer when I wrote it, so don't take it as an example of how you must do things. Regardless, it does work. I've continued to use the character stream code in every text parser I've written since, with some improvements.

When I was working on one paid git I’ve come up with a kind of engine that was driven by a JSON file. It was a kind of interactive game or very poor text adventure game. I’ve asked the person for whom I created this project if I can publish the game so others can use it. It was very cool. Later I came up with something even better. My own programming language that compiles into JavaScript. The project is in Beta version and I still need to work on the playground and documentation. You can check it out. Here is Gaiman’s GitHub repo. If you want to create a complex project with user interaction, it may be easier to do this with Gaiman, since it simplifies things. The same code in JavaScript will be much more complex.

I've created programming language based on Ruby that simplifies creating Terminal text-based games and applications in the browser. I've released first 1.0 beta version, but I'm still adding features and fixing bugs. I yet need to add more documentation and improve Gaiman playground.

The repo for the language can be found on GitHub: https://github.com/jcubic/gaiman the only documentation so far is the Wiki with Reference manual https://github.com/jcubic/gaiman/wiki/Reference-Manual

I've released the first 1.0 beta version of Gaiman. I'm doing small tweaks but it seems that all language features are there. But I need to improve code coverage so I know that everything is tested. And I need to stress test a bit my parser so I know that odd syntax combinations works.

I've just published the first beta version of Gaiman 1.0 to NPM.

in Gaiman language that compiles to JavaScript, I have syntax like this:

I've wanted to have my own programming language, that will make it easier to create text-based adventure games for my Open Source project jQuery Terminal. The idea for the language came after I've created a paid gig for one person, let's call him Ken, that needed this type of game, where the user interacted with the terminal and was asked a bunch of questions and it was like an adventure game, related to Crypo. The code I've written, that Ken needed, was data-driven by a JSON file. It was working nicely, Ken could easily change the JSON and have the game changed however he wanted. I've asked if I could share the code since it was a very cool project and Ken agreed that I can do that two months after he publish the game. But after a while, I've realized that I can have something much better. My own DSL language, that will make it simpler to create text-based adventure games. A person with a bit of programming knowledge like Ken, could easily edit the game, because the language will be much simpler than complex JavaScript code that is needed for something like this. And even if I would be asked to create a game like the one for Ken, it would be much easier and faster for me. This is how Gaiman programming language has started.