[Wazako]

typing saves so much time. Especially since the flexibility of its optionality does not restrict, and allows for really nice autocompletions.

Especially with esbuild which has made this simple and fast, one could even say it has saved javascript.

[pier25]

I have ample experience with typed languages like C++, C#, Java, Kotlin, Go, AS3, Swift, etc.

Maybe I just have exceptional memory but I rarely encounter a problem that would have been solved by using TS.

[Scarbutt]

It's about big codebases and team use, not about you.

[hot_gril]

Typing wastes time. Teammate and I tried switching a backend project to TS, and I kept a mental note of time spent defining types vs time saved not debugging type-related issues. The result was some high number vs 0. Also messed with the toolchain, making things like Node profiling not work.

[yCombLinks]

If you already have an existing, functioning codebase, adding types is not saving you time (right now). It's akin to adding a lot of unit tests. You gain time later, and often indirectly from others not making mistakes your types would prevent.

[tomtheelder]

Is it a solo project? The time savings of typing is really a function of project size and number of collaborators. For a small, solo project it’s either neutral or a negative.

[capableweb]

Believe it or not, autocomplete is still possible without typing, as any user of any dynamic language could tell you. Seems like a poor reason to add a another full language to the abstraction ladder of your application.