[qwertyuiop924]

Besides, while JS's problems are very real, they're quite exaggerated. It's still a perfectly usable language, even without TS and whatnot.

And unlike some languages used for app programming, an error doesn't have the potential to hand you a segfault.

[tempodox]

> ...an error doesn't have the potential to hand you a segfault.

And that is a good thing why? So you don't realise there was an error and your app runs on in a corrupted state?

[aurelianito]

For starters, a huge set of security vulnerabilities are not possible. Ex: buffer overflow, double free, reading uninitialized memory.

[qwertyuiop924]

Precisely. Don't write Application code in a systems language.

[qwertyuiop924]

If you segfault, that's not because your state is corrupt. Not usually, anyways. Typically, you'll segfault from a use-after-free error or similar.

[tempodox]

How else would you define corrupted state than “losing track of the objects in your app”? Not crashing as a consequence hardly makes it better.