3 ms·

1) JavaScript is NOT C. 2) There is nothing wrong with C. It was DESIGNED to service specific needs and does that just fine 3) I think this obsession with "sa

by FpUser 7y ago

1) JavaScript is NOT C. 2) There is nothing wrong with C. It was DESIGNED to service specific needs and does that just fine 3) I think this obsession with "safe languages" is being taken too far. Safety does not come free, we pay for it. Mostly in performance which is a valuable "feature" for many types of software. Not gobbling all computer memory running "Hello world" helps too. Besides automatic memory management and "everything is immutable" does not really make software safe either.

timw4mail 7y ago
3) It's not "safe languages", it's "memory safe languages". The whole point is to make very common security vulnerabilities due to unsafe memory usage much less common. Rust and garbage-collected languages have memory safety. C/C++ do not. That's the whole point.
- FpUser 7y ago
  C/C++ have enough tools to detect and get rid of memory leaks. Quite frankly memory safety ceased being a practical problem to me years ago.
  - timw4mail 7y ago
    That assertion would carry much more weight if not for the constant barrage of security vulnerabilities due to memory issues.