3 ms·
If you're starting a new system-level project, you should be using C++ or Rust, not C and certainly not Go (which was designed for kids to write microservices w
by bitwize 10y ago
If you're starting a new system-level project, you should be using C++ or Rust, not C and certainly not Go (which was designed for kids to write microservices with; in other words it competes with Ruby and Node, not C++). A modern language should support static typing with parametric polymorphism and statically determined object extent for most objects (with well-defined extent for the rest). Rust also gives you statically determined object access.
- microcolonel 10y agoHow can you, knowing absolutely nothing else about the use case, suggest a solution? What if they're on an architecture where the libc++ or rust runtime is low quality? What if their application needs to be NUMA aware? There are plenty of reasons not to use C++ or Rust. They are not magic bullets which solve all engineering challenges.