[arcanon]

How so? Coffeescript was mostly absorbed by JS, a true success story. The cutting edge JS ppl are moving away from TS right now, at least some of the ones I follow on twitter seem to be over it. OP might be on to something, not wanting to waste time chasing trend n-1

[Zababa]

Intertia. TS is way more popular than Coffeescript ever was, so there will be more code to maintain, and the network effect applies here.

> The cutting edge JS ppl are moving away from TS right now, at least some of the ones I follow on twitter seem to be over it.

Who are these people, why are they moving away from it?

> OP might be on to something, not wanting to waste time chasing trend n-1

If you need static typing for JS now, TS is your best bet. You can also wait N years for TC-39 to add it but so far nothing has been proposed.

[arcanon]

It seems to me that there is a divide of angular typescript apps that are about 3-5 years old and a new wave of react flow apps. Wonder what the stats are.

[Zababa]

That might be just my bubble, but I've never heard of anyone using Flow, especially with React, whereas I often hear about React with TypeScript.

[mcphage]

> The cutting edge JS ppl are moving away from TS right now, at least some of the ones I follow on twitter seem to be over it.

What do you see them moving to?

[arcanon]

Linky: https://www.google.com/amp/s/startfunction.com/deno-will-sto...

[Zababa]

This is just a Deno-specific internal thing due to tsc being too slow for their specific case. Deno itself can read and execute TS code and they aren't planning on dropping that.

[arcanon]

Right, they just wouldn’t use it themselves.

[Zababa]

In the original design doc: https://docs.google.com/document/d/1_WvwHl7BXUPmoiSeD8G83JmS...

> Update June 10 2020: I saw that this design doc was being discussed more widely. Most people don't have the context to understand this narrow technical document - it is only applicable to a very particular, very technical situation in the internals of Deno. This is not at all a reflection on the usefulness of TypeScript in general. It's not a discussion about any publicly visible interface in Deno. Deno, of course, will support TypeScript forever. A website or server written in TypeScript is a very very different type of program than Deno - maybe much more so than novice programmers can appreciate - little of Deno is written in TypeScript. The target audience is the 5 to 10 people who work on this particular internal system. Please don't draw any broader conclusions.