Yeah, sure. The original motivation behind starting to think in that direction was that up until that time we have been a vendor of tools, and while people can be passionate about the tools they are using, tools are not that hard to replace, like development tools. People can switch to a different editor, to a different IDE, a different continuous integration server, and so we felt like our company had somewhat like an auxiliary role in the marketplace, and we started thinking about ways how we can be more influential.

The way many other companies do that, for example if you look at Twitter or LinkedIn, they are producing lots and lots of infrastructure software that they promote for other people to use, but for us this was not really a good path, because we were actually building desktop applications and we simply did not have the kind of infrastructural software that we could share with a significant number of other people, so we just thought about different approaches.

The idea of creating a language came to our minds because we felt like we had the expertise required for that, because we were building tools for programming in many different other languages, we had IDEs for Java, .NET, Scala, Groovy, Python, PHP, Ruby, JavaScript at that point, and we still did not see any alternative to Java that would be enjoyable for us to use. So we thought that with that expertise why couldn’t we try and build our own language?

As it happens, we find that problems that we have are usually problems that other people in the industry have as well, so we decided that if we feel that unmet need, then there probably are other people who are in the same situation, so there might be some interest in the language. That’s basically where it started from.