3 ms·

Same problems with linters: people write weird code and/or introduce unnecessary changes to correct code that doesn't pass the check. Also, optional type check

• mercurial 10y ago
  > Same problems with linters: people write weird code and/or introduce unnecessary changes to correct code that doesn't pass the check. Having just converted a bunch of pure Javascript to Typescript, and writing new code in Typescript, this hasn't been an issue. > Also, optional type checkers throw away a lot of the upsides of type systems (safe refactoring, type-aware optimizations, useful generics) so they're kind of a worst-of-both-worlds solution. I'm not sure what you mean by "throwing away safe refactoring" but yeah, you don't get the performance benefits or reified generics (not that it's particularly useful). That said, it's not like you derive any performance benefit from Java generics either.