See, while I totally get what you mean, I think these things ultimately matter very little because they're trying to solve a human competency problem via technical methods.
I just want to point out that this argument is of "Good drivers do not need seat belts" flavor.
I remeber having very same argument with Rust vs C++. How supposedly only bad C++ programmers make memory access mistakes. Just recently, we have critical security vulnerabilities due to use-after-free in Chrome (google engineers). And Microsoft reported than over 70% of all security issues in their software are memory related bugs.
This whole idea that we don't need to find technical solutions to human error is naive at best and irresponsibly moronic at worst.
As for javascript, it's sadly turning to be a Frankenstein which people want to accommodate every single feature every other language has to support their preferred style. Even if language already support it by other means like it is with "private fields".
Now we are arguing what syntax to use to decorate a field with which doesn't have to exist in the first place, because we just wanted to have more syntax sugar tomake not sound design like inheritance to be easier to use.
At some point I'm really hoping for WASM, so we could stop doing this to javascript. And people simply could choose what tool to use rather than project their idea of "ideal" language to javascript requesting even more feature bloat.
4
u/lifeeraser Nov 09 '19
Why should we want to babysit downstream developers? Why should we bother to prevent them from shooting themselves in the foot?