4 ms·

Honestly, ask yourself _why_ you think you need strongly typed JS. Are type errors the most common source of errors in JS? Not even close. So why add another

Honestly, ask yourself _why_ you think you need strongly typed JS. Are type errors the most common source of errors in JS? Not even close. So why add another level of complexity for negligible gain.

alcover 6y ago
> ask yourself _why_ you think you need strongly typed JS Because I -and everyone- need a faster, less energy-wasting JS. > Are type errors the most common source of errors in JS? They happen. And could be caught at compile-time under a stronger type system. JS is used client-side in many banking/crypto webapps. I know everything is validated on the server but still presentation is done by JS with its nutty casts/coercions...
- muzani 6y ago
  Parent comment has a point - the appeal of JS is that it's a weakly typed, hacky language. I love duck typing. I don't use Typescript, nor would I use a JS++. There are a good number of programming languages. Why not something like Go? I heard Go compiles to JS, but never tried it. Why is JS even used for banking, and why would converting to a JS++ be easier than adopting something else?
  - alcover 6y ago
    > duck typing hacky language It may be possible to keep duck typing for objects while introducing fast unambiguous primitives like int64_t ? > Why not something like Go? Because JS syntax is very nice - that's my premise. Moreover, client side has to be JS, no other choice yet.