Maybe it’s the evil smell emanating from the keyword “let”. This is the disgusting spoor of the organisation that gave us Visual Basic, keeping alive for decades after its natural life one of the worst “educational” languages. Its presence doesn’t fill me with enthusiasm about the new language.
The thing is, though, there are already a plethora of frameworks for web development. There are Spring, Django, Node.js, several front-end frameworks including Angular, React, Vue and probably one more for each web developer on Earth at this rate. And they all do variations on the same things — rendering the front-end and mapping HTTP calls to functions at the back end. YAML stands for “yet another markup language”, in a fitting piece of self-knowledge. It can only be a matter of time before Yet Another Web Framework acquires a catchy acronym.
Having been in the software game since the mid-80s, I’ve seen a lot of languages come and go, and a few persist and grow. By-and-large, successful languages have been based on C syntax, with Python as a salient exception. The best tools out there are language-agnostic, by which I mean that you can connect the IDE and other GUI tools to compilers and debuggers of your choice. Eclipse and IntelliJ are good examples of these, as they let you build and debug in many languages using the same IDE. Maven, Jenkins and so on cover different parts of the software experience in a similarly flexible way.
What needs to be done — and I’m talking to YOU, fellow developer with time on your hands — is to adapt an existing language to do what Typescript does. Think about it in terms of Java. Java runs on a virtual machine. It’s not the only virtual machine. There’s Rails, on which Ruby can run, and .NET, on which unspeakable things run. Nor is it the only language which runs on the Java JRE; there are Kotlin, Scala and even a Python port. The image which should be forming is that of more than one language which can already be compiled into bytecode running on more than one virtual machine.