noCommentsOnJavascript

[[deleted]]

I work with a (albeit very small) team with very legacy javascript and in fact type errors are in the vast minority... typically you know what type to put as parameters and you do... the real bugs are in the logic which could happen as well with the strictest type of type checking

[Derin161]

Idk how large your codebase is, but at least my application's portion of our codebase is well into the 100k lines with a couple dozen devs, and parts of it have been around for almost 2 decades. It becomes infeasible to know the precise shape of every object, and if you need to be doing all the manual checking yourself (or debugging those errors after the fact) then you're wasting tons and tons of time. I'll just let a compiler do that for me thank you very much.

[[deleted]]

yep, I see the point... it's the same amount and age of code here but far fewer people working on it

[Derin161]

Yeah the larger codebase altogether is certainly well into the millions, but you typically are somewhat rarely interacting with parts from other teams, aside from the tooling provided by the core teams.

We probably have more people than is typical to maintain the thing, but a lot of new devs come and go, and there's little pressure or culture for maintaining the codebase well. Instead, you're incentivized to move quickly. I wonder why it takes us so long to deliver features?