Node.js adds experimental support for TypeScript

Post by ignoramous » Thu, Jul 25, 2024, 3:57 PM UTC

sesm wrote: post #357

winter_blue wrote: post #35

Earlier quoted context omitted.

Flow (by Facebook) used to be fairly significant in the JavaScript several years ago, but right now it's somewhat clear that TypeScript has won rather handily.

There was no real competition, Flow was a practical internal tool with 0 marketing budget. Typescript is typical MS 3E strategy with a huge budget. Needless to say, Flow is much more practical and less intrusive, but marketing budget captured all the newbie devs.

Post by winrid » Thu, Jul 25, 2024, 4:00 PM UTC

Post by sroussey » Thu, Jul 25, 2024, 4:02 PM UTC

tracker1 wrote: post #340

murmansk wrote: post #185

Earlier quoted context omitted.

[flagged]

JSDoc is also helpful in dealing with multiple argument option types for a function or constructor, which won't show in TS alone.

Post by teaearlgraycold » Thu, Jul 25, 2024, 4:05 PM UTC

WorldMaker wrote: post #342

zarzavat wrote: post #120

One thing to note is that it is impossible to strip types from TypeScript without a grammar of TypeScript. Stripping types is not a token-level operation, and the TypeScript grammar is changing all the time. Consider for example: `foo ( x )`. In TypeScript 1.5 this parsed as (foo (x)) because bar&baz wasn’t a valid type expression yet. When the type intersection operator was added, the parse changed to foo (x) which…

The syntax from the perspective of type stripping has been relatively stable for more versions of Typescript than it was unstable. You had to reach all the way back to 1.5 in part because it's been very stable since about 2.x. The last major shift in syntax was probably Conditional Types in 2.8 adding the ternary if operator in type positions. (The type model if you were to try to typecheck rather than just type-stri…

Post by kcrwfrd_ » Thu, Jul 25, 2024, 4:14 PM UTC

lolinder wrote: post #306

nyssos wrote: post #301

Earlier quoted context omitted.

There's not much connection. Typescript's record types aren't sound, but that's far from its only source of unsoundness, and sound structural typing is perfectly possible.

Soundness is also a highly theoretical issue that I've never once heard a professional TypeScript developer express concern about and have never once heard a single anecdote of it being an issue in real-world code that wasn't specifically designed to show the unsoundness. It usually only comes up among PL people (who I count myself among) who are extremely into the theory but not regularly coding in the language. Do…

  let foo: number[] = [0, 1, 2]

  // typed as number but it’s really undefined
  let bar = foo[3]