Design Doc: Use JavaScript instead of TypeScript for internal Deno Code

Re:Design Doc: Use JavaScript instead of TypeScript for inte... by tuckerconnelly on Monday June 08, 2020 @11:01PM (#23463203)

I feel the exact same. Reminds me too of Nassim Taleb's idea that, if something as already existed X years, it's likely to exist another X years. I'm skeptical of the staying power of these transpilers.

[ Parent | on HN ]

Re:Design Doc: Use JavaScript instead of TypeScript for inte... by zelly on Monday June 08, 2020 @11:48PM (#23463469)

Lindy effect

https://en.wikipedia.org/wiki/Lindy_effect

Transpilers definitely aren't Lindy. CoffeeScript, GWT, Elm, among others form a huge graveyard of de facto defunct languages targeting JS.

[ Parent | on HN ]

Re:Design Doc: Use JavaScript instead of TypeScript for inte... by francis36012 on Monday June 08, 2020 @11:20PM (#23463335)

Typescript has been around since 2012. Going by the quote, it is likely to still be around in the next 8 years.

[ Parent | on HN ]

Re:Design Doc: Use JavaScript instead of TypeScript for inte... by AaronFriel on Tuesday June 09, 2020 @01:05AM (#23463819)

TypeScript has been around since 2012, and it has since won in the marketplace of ideas, becoming the single most popular language to transpile to ES# and beating a well-resourced competitor in Flow.

The type war was "won" by TypeScript, and I expect it's just a matter of time before types make it into the standard. The benefit of winning so completely and having such enormous popularity is that its ideas are very likely to make it into the standard such that no transpilation will be necessary.

[ Parent | on HN ]

Re:Design Doc: Use JavaScript instead of TypeScript for inte... by lioeters on Tuesday June 09, 2020 @12:02PM (#23467789)

> just a matter of time before types make it into the standard

I hope so too. TypeScript has done so many things right in its design and implementation - starting from Anders Hejlsberg, with expertise in creating numerous languages; backward compatibility to allow gradual and seamless migration from JS to TS; structural typing; editor/IDE integration via language server; good documentation; corporate backing (maybe not necessary, but like React, I think it was a big factor in its wide adoption).

[ Parent | on HN ]

Re:Design Doc: Use JavaScript instead of TypeScript for inte... by coding123 on Tuesday June 09, 2020 @10:37AM (#23467022)

I don't understand. So in 2016, Typescript was around for 4 years so it only had 4 years left, yet here we are.

[ Parent | on HN ]

Re:Design Doc: Use JavaScript instead of TypeScript for inte... by jatone on Tuesday June 09, 2020 @02:25PM (#23469234)

its 'at least another X years'

so in 2016 typescript was around for 4 years, and here we are now 4 years later. its still around. seems to be holding.

[ Parent | on HN ]