You really should just not assume things about people with no reason other than "they dont like the things i like so therefor they must not be experienced". I've worked on plenty of very very large codebases with large teams.

> What a nonsense. Perhaps read history of TypeScript and you'll learn why it was created.

did you? it was created by microsoft, a C# shop, to support their existing workflows around typing and hinting support. The typescript creation team was literally led by the guy who made C#.

▲

jakubmazanec 2 hours ago | parent | next [-]

> You really should just not assume things about people with no reason other than "they dont like the things i like

That's not the reason for my comment. I truly don't understand how after so many years someone "isn't sold" on TypeScript. Sure, you don't have to use it if you don't want to, but if don't see how it's truly essential in current JS development, I don't know what else to assume, other than OP doesn't have enough experience.

> it was created by microsoft

It was created at Microsft, but it was crated by Anders Hejlsberg who, I'm pretty sure, didn't want to just "create a safehaven to C# and java devs", he was actually solving real problems with JS development, completely orthogonal. You can argue that TS's first syntax was very C/C# inspired, and that Anders also created C#, but that's not what OP meant (or at least how it read).

	▲	austinthetaco 4 minutes ago \| parent [-]
		Its not essential. Good organization. Good functional configuration. Proper separation. Good variable naming. All of these things are what make it more than easy to work without type declaration. People have been working on huge code bases without types for a VERY long time with no issue, especially in functional paradigms.

▲

tomnipotent 19 minutes ago | parent | prev [-]

> You really should just not assume things

And yet you follow this up by making assumptions about the motivations behind TS. Anders has mentioned that TS was purely motivated by internal MS teams struggling with huge JS codebases, nothing to do with C# but clearly his work on other languages would have influenced how he approached designing the language.

	▲	austinthetaco 7 minutes ago \| parent [-]
		They have said time and time again it was because their C# team was writing frontend code in a huge codebase and wanted similar support.