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...
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?
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.