stmfd

4 ms·

1. 1.▲
   by stmfd 10y ago

   Let's look at Rust's homepage: - Zero-cost abstractions - C++, in my opinion, is the founding father of zero-cost abstractions. - Move semantics - we've had this since C++11. - Threads without data races - C++11 introduced a
2. 2.▲
   by stmfd 10y ago

   I agree, that was rather brash. They're not bad programmers. I tried to clarify that in my previous comment. I think C++'s biggest failing is how large and convoluted it is but, in relation to the thread's question, how many
3. 3.▲
   by stmfd 10y ago

   My views are the responses you'll probably get from the people who've been doing systems programming in C for the past 20 years. I don't doubt lots of common applications have memory issues. Maybe not a definite segfault but
4. 4.▲
   by stmfd 10y ago

   I think the bad programmers are ones who state "segfault protection" as a feature of Rust because they read it on Rust's site. I genuinely don't think these features of Rust are really all that useful (they're bein
5. 5.▲
   by stmfd 10y ago

   I think it has a fair chance (Go is a "systems" language and grew very quickly). I also believe you'll see it pop up in unikernels as well. Why, you ask? Because there's always 1 person that starts a project that gets tr