4 ms·

> compiling/transpiling/whatevering webpack with webpack for webpack development would make no sense as far as I can tell Isn't that the workflow when working

• patates 5y ago
  It does make sense with TypeScript as it's a language. It, however, does not make sense with "tooling" (IMHO - there may be of course obvious stuff I may be missing). Tooling may also use a transpiled language but again, I, as a developer who's very experienced with JS, don't see a big win there. Someone mentioned Flow + OCaml as a bad example and how it doesn't work out for them, but that's more than tooling. At that point you are not using tools written in other languages to build JS, you are just using other languages.
  • de_keyboard 5y ago
    Flow failed because Microsoft enabled TypeScript by default in VS Code. It had nothing to do with OCaml in my opinion. However, TypeScript is now suffering from long compile-times because it targets JS. If it was implemented in a language with more control over threading etc. I think it could be faster.
    • patates 5y ago
      I think there were attempts to rewrite a subset of TS in another language. I don't mean assemblyscript, no. Also, if I could use TS on the backend without node (say, with the lib/runtime of another language), that would be amazing.
      • guipsp 5y ago
        Deno exists, I guess
• IshKebab 5y ago
  Yeah and Typescript's type checker code is one 41k line file because if they split it into multiple files it will be slower. `tsc` is pretty great to be honest but it feels like the exception.