I don’t think so. There are so many languages around to get enough experience with what works well and what doesn’t for languages.
A theory of parsing has been well developed decades back. It helps to create a prototype of interpreter and/or compiler really fast and for cheap.
However, like in a case with a hammer for construction works, there’s a linked infrastructure around one should necessarily take care of. Languages usually support a basic set of features. End users usually want a wide spectrum of possibilities. So, what’s in between? There are numerous interlinked API’s in a whole cloud of libraries and toolkits.
When binary compatibility with 3rd party software isn’t supported, sooner or later a very important question raises up: How at least a minimal set of API’s can be ported under umbrella of a new language? A typical answer today sounds like this: Let’s make new language open source and free.
It works. However, two issues flash on the road:
- What is so interesting in new language to attract busy developer’s attention and their desire to keep patience on bugs of developing language?
- How to manage a chaos of numerous API’s, growing up as mushrooms around the globe, often of little quality, local purpose and having no actual documentation? I hint to R and Python worlds, sorry, guys.
When you see a clear road in between of named obstacles, go ahead! Software brings a real fun to those who loves it! Good luck!
Image credit: image with no confirmed source; last seen at Dionisio Gutierrez