When you code for the web, sometimes you just wish that your pseudo code would just work instead of having to turn it into PHP, Ruby, or Python. In this panel, Jim Barcelona shares how he went about creating a new language, Mojo for the Web.
Questions Answered:
What is an interpreted language?
Why should I write my own interpreter?
What resources or help can I get when writing my own interpreter?
How well does Mojo for the Web scale?
How long did it take you to write Mojo for the Web?
What databases are supported for Mojo for the Web?
Are there any websites that run Mojo for the Web?
What language features do you regret not putting into Mojo for the Web?