typescript

It's Microsoft, Eich & co that pushed the class syntax based on ideas that originated in TypeScript.

TypeScript is probably more refined and has better tooling than Flow as it's a lot older.

That's more due to AMD, but TypeScript adds some nice syntax sugar on top of that.

It turns out TypeScript hit that spot well enough and Anders was right about that.

You just have to declare which external module (3rd party dep) you are using so typescript knows how to apply typings.

The parts that are actually TypeScript itself are very much more restricted and really are just bits around the type system.

In practice, Flow caught essentially no real errors that Typescript did not, and vice versa.

That's why things like TypeScript exist and it makes OOP easier among other things.

I've been playing with Typescript in both Visual Studio and Visual Studio Code and Intellisense is great.

I am wondering if Phaser with TypeScript would make things easier for someone like me who like static typing.

When I moved my team's JS code to typescript, I found myself way way faster with the improved intellisense.

Flow is not available on windows, typescript is available on all major OSes.

When a new project starts up, the question is usually " Is there a compelling reason to use plain JavaScript instead of TypeScript here?

However, people want to do much more complex apps with Javascript without having to mess around with Typescript, Babel transpiler, etc.

Typescript covers pretty much all the ES6 features that I use while flow is still missing let/const apparently.

Both languages have warts, but JS is a small enough language (at least in the ES5/ES5+Typescript world I was working in) that the warts felt finite.