Vanilla JavaScript is untyped by nature, some will call it “smart” because it is able to figure out what is a number or a string.
This makes it ea...
For further actions, you may consider blocking this person and/or reporting abuse
I still like writing plain old Javascript like we did in the good old days, but when I work with 50 people in 3 timezones on a large project, I currently prefer typescript (the tooling is really a differentiator).
My appreciation for TypeScript grew out of maintaining the same two JavaScript projects over a 5 year period. Writing POJS is fine, but if your project doesn't have a finite scope, or you have multiple contributors, the additional structure provided by types pays huge Dividends in the long term.
While a type system won't improve my personal code it would drastically improve team productivity and code maintenance burdon when someone else needs to maintain my code. Basically from hell to heaven, tooling, early error check. Code can be good either way, maintenance definitely not.
We have this habit of beating around the JavaScript bush using transpilers to hide its non-classical behavior. I have trouble justifying the extra build step just to arrive back at good ol' js.
Yep, I definitely wouldn't recommend it for every single project, especially not when working through an experiment or proof-of-concept. Static analysis can be a bit tiring but it gets stronger as the codebase increases significantly.
I could definitely see where JavaScript could become unwieldy in larger projects. For people who've learned class based languages, typescript offers a great abstraction from js oddities.
Try Nim lang, better types and compiles to JavaScript.