Glimmer.js: What’s the Deal with TypeScript?

  1. “JavaScript-alikes” like CoffeeScript will have to break their own backwards compatibility, or diverge from JavaScript (and thus become less JS-alike over time).
  2. Languages with totally different syntax and semantics, like ClojureScript, are difficult to debug, even when source maps are working perfectly.
  1. All of that extra type syntax is optional; only use it if it’s bringing you benefits.
  2. Don’t get fooled into thinking that TypeScript is as awkward and occasionally frustrating to use as Java. Behind that Java-like syntax is a language that is every bit as flexible and dynamic as JavaScript because, well, it is JavaScript.

JavaScript + Types = TypeScript

“But I Still Don’t Want to Use TypeScript!”

“That’s what Angular said and look how that turned out.”

Member of the JavaScript glitterati.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Why Are Freelance Programmers So Expensive?

JavaScript Studio publicly available

A Serverless Cloud for Stateful Applications

Fundamental React.js Concepts

Tutorial: Serial Communication with Arduino and p5.js

10 Things That Will Make You a Worse Programmer

Why , How, When to use CSS BEM?

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Tom Dale

Tom Dale

Member of the JavaScript glitterati.

More from Medium

React — JavaScript vs Typescript

Typescript(ing) React.cloneElement or how to type a child element with props injected by the parent

How to Detect when All Images are Loaded in a React Component

Forcing string patterns in Typescript