3 ms·
"If your newest tool is a hammer, every problem looks like a nail." There is hardly any language that doesn't have some kind of meta language that compiles to
by misja111 4y ago
"If your newest tool is a hammer, every problem looks like a nail."
There is hardly any language that doesn't have some kind of meta language that compiles to JS. And without exception they all are bad, except maybe if you have a backend which only needs some very basic front end which you prefer to write in the same language.
But with any decent sized front end project, JS or TS are the better choices. JS, obviously, because it runs natively in the browser. So all browser tooling works out of the box, debugging is easy because what you see is what actually runs.
TS, although it doesn't run natively, at least was designed to be compiled to JS and is widely supported so tooling is good as well.
But any JS substitute that was added to a backend language as an afterthought will suffer:
- inferior tooling
- more troublesome debugging
- and last but not least, because it was added as an afterthought, 95% of the language will work fine but the other 5% can give you as a developer serious head aches.