When deciding whether or not to use a transpiler, it ultimately comes down to your goals, team dynamics, project requirements, leadership preferences, and overall vision.
Instead of asking "why should I use a transpiler," consider the question of which technology aligns best with your skills and those of your team. For instance, if you are working with a Ruby program, CoffeeScript may be a more seamless choice. On the other hand, if Java is your strong suit, options like GWT or Vaadin could be worth exploring...
Javascript serves as the foundation for web development, but if you wish to implement advanced concepts or experiment with alternative syntaxes and paradigms, then utilizing a transpiler becomes necessary.
Various transpilers exist in the market, catering to different needs such as Objective-J with Cappuccino, GWT by Google, Typescript for type enforcement, Eml for functional programming, Babel for ES7 to ES5 conversion, among others.
Additionally, some frameworks like Vue.js, React, and Flow utilize transpilation internally (unlike Angular 4). Writing a high-quality interpreter with a JIT compiler often requires significantly more time and effort compared to using a language transpiler that converts code to Javascript efficiently.
Furthermore, there's the issue of standardization to consider. Using a transpiler allows Forth enthusiasts to develop applications in their preferred language and then convert them to ES3 for widespread browser compatibility without the need for additional plugins.