3 ms·
Note that things are a lot better now than they were in 2018, in large part due to his work and his team's. The typescript migration has gone well, with good au
by jefftk 5y ago
Note that things are a lot better now than they were in 2018, in large part due to his work and his team's. The typescript migration has gone well, with good automatic migration tooling, and I mostly only use TS now. This means good error messages, and good editor support.
(Disclosure: I work on ads at Google, speaking only for myself)
- lolive 5y agoHow did you do the work to type all your existing JS libs, so they have a clear TS contract?
- jefftk 5y agoAll of our existing JavaScript libraries were already typed, but with the awkward "types in comments" system: https://github.com/google/closure-compiler/wiki/Types-in-the-Closure-Type-System https://github.com/google/closure-compiler/wiki/Types-in-the... Their team only (though it's a big "only") needed to do the work to make this existing type info available to TS
- lolive 5y agoI am rather new with JS, TS and all that. But did not IntelliJ have some JSDoc support to help it autocomplete JS, a long time ago?