-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
>> C is not memory safe. It suffers from undefined behavior. These are valid complaints. However, C code can be secure!
The lack of memory safety and undefined behavior that is difficult to reason about is why C and C++ are being displaced by Rust.
https://blog.regehr.org/archives/213 gives great insights into how undefined behavior in C and C++ can be difficult to reason about and cause problems.
I agree with Drew that Rust is not perfect and it still needs to target more architecture and platforms, get a formal specification, and more implementations, but it is the most promising alternative to C and C++ so far and it has a bright future with the recent Rust Foundation: https://foundation.rust-lang.org/
While Rust seems like a great programming language, I have come across some criticisms of it which appear to have some validity. Comparatively more impactful than what Drew describes here is the trademark problem that's listed on Hyperbola GNU/Linux site's webpage titled Rust's Freedom Flaws: https://wiki.hyperbola.info/doku.php?id=en:main:rusts_freedo...
*Please be aware that the rust project is now independent of Mozilla, so the following is not based on the latest information available.
Rust and also Cargo (the Rust package manager) violate the freedom to redistribute without “explicit” approval. Their trademark license imposes requirements for the distribution of modified versions that make it inconvenient to exercise freedom 3. The Rust's Media Guide says it merely supplements the official Mozilla trademark policy; it doesn't replace it. Since their trademark policy applies, then everything in that list (including Rust and Cargo) pulls in the same issue as Firefox and Thunderbird.
In short, Mozilla won't be happy with us applying patches and modifications to their trademarked language without “explicit approval”, except for non-commercial usage, so it is a freedom issue. For further references, there is a report in Rust about those trademark restrictions and Niko's response (one of the members of the Rust Legal Team).
I'm not an expert in this stuff, but this sounds like it could bear some weight. Currently the problem has not been resolved and it is still a matter to be considered by the rust board. Here is the latest thread on the problem I could find on the rust-lang GitHub: https://github.com/rust-lang/foundation-faq-2020/issues/35