[eksemplar]

I especially don’t get the ide support bit, because Visual Studio Code already does that for regular JS.

I think typescript is s mistake that most people will regret because it adds so much complexity to the process for so few advantages gained. I mean, we were predominantly a C# house, if anyone should be using Typescript it should be us, but we found it to be much less productive than JS exactly because stuff like prototypes becomes more complex and typesafety kind of gets in the way of the process when you’re not exactly sure what you’re making.

I don’t think it’s exactly coffeescript though, I mean, I just ranted about typescript, but it doesn’t get in the way like coffescript. Since it integrates sort of decent into JS, it’s not a horrible thing, we just found it unnecessary.

[james-mcelwain]

> I especially don’t get the ide support bit, because Visual Studio Code already does that for regular JS.

The IDE support in VSCode is at least partially driven by type declarations from TS projects, so regular JS is benefiting from TypeScript.

[eksemplar]

I didn’t say typescript was horrible, it’s just been unnecessary and unproductive for us. I think it does have a place in applications like VS code, because maintaining them is quite a lot bigger than most projects, and you don’t include VS code in yours.

[johnny22]

if you're not sure what you're making then just type everything you're spiking on with any or unknown?