How do you choose between native web development languages and transpiling?

1 What is transpiling?

Transpiling is the process of converting code written in one language to another language that has a similar level of abstraction. For example, you can transpile TypeScript to JavaScript, or Sass to CSS. Transpiling is different from compiling, which converts code from a high-level language to a low-level language, such as from C# to machine code. Transpiling is also different from interpreting, which executes code directly without converting it to another form.

2 Why use transpiling?

Transpiling can offer a range of advantages for web development. For instance, it can enable the use of newer features not supported by the target language or environment, such as TypeScript for static typing and object-oriented features in JavaScript or Sass for variables and mixins in CSS. Additionally, it can enhance the performance, readability, or compatibility of the code, like Babel for transpiling modern JavaScript syntax to older versions that are compatible with more browsers or CoffeeScript for concise and elegant code that transpiles to JavaScript. Moreover, it can integrate with other languages or frameworks that use a different syntax or paradigm, such as JSX for HTML-like elements in React or Emscripten for transpiling C++ code to WebAssembly.

3 Why not use transpiling?

Transpiling can present some drawbacks or challenges for web development, such as complexity and overhead in the development process. This is due to needing to set up and maintain the tools and configurations for transpiling, as well as dealing with potential errors or bugs that arise from the conversion. Additionally, transpiling can reduce the control or transparency of the code, making it difficult to debug or optimize. Furthermore, it can increase dependency on external libraries or frameworks, requiring polyfills or shims to make the transpiled code work properly, or relying on specific features or conventions that are not standard or widely adopted.

4 How to choose between native and transpiled languages?

When deciding whether to use native or transpiled languages for web development, there is no definitive answer as it depends on various factors. For instance, project requirements and specifications may limit the choice of languages, while a developer's personal preference and experience may influence their decision. Additionally, the trade-offs and costs of transpiling should be considered, such as the development time, quality, and maintenance of the code, as well as the compatibility and accessibility of the web application. Ultimately, the choice of language should be tailored to the needs of the project.

5 Tips for using transpiling effectively

If you decide to use transpiling for web development, there are a few tips to keep in mind. First, choose a transpiler that suits your needs and goals. This could include features, syntax, or style preferences as well as integration with tools, platforms, or frameworks. Second, make sure to test and debug your code thoroughly. Source maps can be used to trace the transpiled code back to the original code and there are tools that automate or simplify the process. Finally, keep your code clean and consistent by using a code formatter or linter for a uniform coding style, and comments or documentation to explain the logic or purpose of your code.

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?