I’m Not a Techie. Please Explain!

Just before we get into the debate of TypeScript and JavaScript, for those who aren’t quite sure what this tech lingo means, we’ll run you through the basics.

TypeScript and JavaScript are both programming languages that software developers use to build projects such as websites and applications.

JavaScript was first released in 1995 by the ‘father of JavaScript’ Brendan Eich. TypeScript is an open-source programming language, developed and maintained by Microsoft. It is a strict syntactical superset of JavaScript and adds optional static typing to the language. Additionally, Typescript is a lightweight, interpreted, or just-in-time compiled programming language. This program first made an appearance in 2012 and promoted a new wave of development.

Since then, there’s been an ongoing debate in the technical world about JavaScript vs. TypeScript.

So What’s the Difference?

Essentially, TypeScript is built on top of JavaScript and includes a more structured approach to development.

While JavaScript provides freedom to build and design, TypeScript includes ‘rules’ and guidelines that developers must adhere to.

A screenshot of Devika utilizing a React framework without TypeScript. Image by Robin Wieruch

A screenshot of Devika utilizing a React framework with TypeScript

The pros of JavaScript include the freedom to build, create, and push developments without being restricted or bound by rules. This makes it a little easier to learn if you’re just starting. In addition to the freedom, many developers prefer JavaScript as they’re more familiar with the language.

TypeScript, on the other hand, has rules integrated within the language. For example, it defines the difference between circles and squares. This means you cannot build whatever you please because there are specifications around the design. A simple analogy is trying to put a square through a triangular-shaped hole. It just won’t work!

Screenshot of an application utilising Typescript (left), Screenshot of an application utilising Javascript (right)

The Downfalls of TypeScript

The most prominent limitation occurs during team project management. Because TypeScript is structured, development teams must understand the ‘rules’ to be able to collaborate on projects. If a team member is not familiar with these rules, there can be a delay in meeting targets and deadlines for a project.

As TypeScript is a superset of JavaScript, some TypeScript projects don’t utilize TypeScript core principles. Instead, they simply treat the project as if it were written in JavaScript. This can create unexpected and difficult to detect errors due to the lack of implementing strict types defined within your code.

But What About the Pros?

Developers who swear by TypeScript often say learning this language makes you a better developer. While it takes a little more effort to learn the rules of the game, it teaches developers to understand the errors of a build. In contrast to JavaScript, TypeScript pinpoints specific issues so that developers can view and quickly resolve these problems. Once your IDE and linting rules are set up, it greatly enhances the developer experience with tools like auto-complete and inline error checking.

Our Stance on the Debate

Possibly a controversial stance, but TypeScript has our vote!

We use TypeScript to manage our client’s projects as well as our website. We’re finding it to be the most effective way to manage information across databases, backend, and frontend processes.

Have a try yourself:

http://www.typescriptlang.org/playground/

Tips for advanced learners:

https://www.typescriptlang.org/docs/handbook/advanced-types.html

Or get in touch with us here.

Our Stance On The Typescript vs. JavaScript Debate