Storyscript the cloud programming language for rapid development of application backends. The language intuitively and seamlessly moves data between microservices, functions, and everything else in the middle providing a monolithic-lens for modern microservice, "serverless" and API architectures in one cohesive, readable story.

Let's discover the top questions the developer community asks about Storyscript to shed light on our decision to design and develop a new programming language from scratch.

Top 3 questions from the developer community.

  1. "Developers are resistant to learning new languages, right?"
  2. "Why not just fork JavaScript?"
  3. "Is this replacing other languages?"

Let's break these down.

Developers resist new languages.

A programming language is a vocabulary and set of grammatical rules for instructing a computer or computing device to perform specific tasks.
– Wikipedia

Configuration is language. Kubernetes and Docker are languages. They have vocabulary, grammatical rules, and perform specific tasks. These technologies have been widely adopted in the market and enterprise.

Frameworks are languages. Angular, React, VueJS, Rails, Django are languages. They have vocabulary, grammatical rules, and perform specific tasks. Developers stay cutting edge and adopt new languages to build the same thing more efficiently.

There was well over 25 languages created (excluding framework and configuration languages) in the last 8 years including Swift, Rust, Kotlin, Julia, and TypeScript; many of which appear in the "top 10 languages to learn in 2019" articles.

The developer is eager to learn new languages that amplify their ability to create and deploy software more efficiently. Developers love to learn and eager to adopt new technology that may make them more productive.

Just fork it.

Isn't is easier to just use JavaScript (or whatever) instead of designing your own language? You would get all the devtools for free, the huge community for free, the mass of knowledge in StackOverflow for free. False.

  1. Unlearning is harder than learning something new.
  2. Good luck branding your fork of Javascript.
  3. Inheriting the dev-tools and their accrued technical debt would be awful.
  4. Hack your own features into the compiler/runtime... No, thanks.
  5. "Hey Support, StackOverflow says I can just import this package".
  6. You still have to install all the forked dev-tools.
  7. Our library is different.
  8. Our runtime is different.
  9. Our goals are different.

Forking JavaScript, or any other language, would cause more confusion and unlearning than it's worth. Plus, it's fundamentally solving a different problem.

Replacing other languages.

Let's be clear. Storyscript does not replace other languages, on the contrary, it uses them all. Storyscript abstracts protocoling and serialization between polyglot microservices, functions and API's. The focus is on readable business-logic acting as a lens of truth over cloud resources. It does not compile to another language, it does not translate to another language and it does not run on one computer. A true data orchestration language, sometimes called glue-code.

Languages have feelings.

One could argue that Python and Ruby, in many ways, do the same thing yet they feel different from one another. The communities behind these languages share different values and have strong pride in their language.

"Ruby is sexy".
               "Python is clean".
"Ruby is beautiful".
               "Python is zen."

We intentionally designed Storyscript to have a certain feeling when programming with it; a feeling that other languages did not capture. When you explain an application or feature to your friend you don't "show them the code", instead you use spoken language to abstract the goals from the code; the story of your code. Storyscript has a native, natural feel to it. The way you read, write and share Storyscript is nearly the same as the story of your code.

Storyscript is Apache 2.0 licensed. Contributions are welcomed with love ❤️ on GitHub.

Learn more about Storyscript in our documentation 🚀