3 ms·
There’s no need to be so aggressive.
by steveklabnik 7y ago
There’s no need to be so aggressive.
- ncmncm 7y agoBy "aggressive", you mean explaining the point in detail? Rust and C++ have different emphases. C++ has a huge head start, but also massive backward-compatibility anchors. It is certain that, over time, Rust will get better at expressing powerful libraries, but C++ is not sitting still. It is very far from clear whether Rust will be important, ten years from now. It is far from clear that it is more beneficial to put resources into rewriting C things from scratch in Rust than to transition existing development from C to C++, and start replacing subsystems in-place. What is clear is that the difference in benefit to starting any new project in Rust or in C++ is absolutely overwhelmed by the absolute benefit of starting in one of those, and not C.
- steveklabnik 7y ago> By "aggressive", you mean explaining the point in detail? No, I mean the stuff dang has already commented on. You also did not explain the point in detail, you responded to what I said with a whole bunch of off-topic things, and then insinuated that I did not have the point. The parent said that C++ would have "memory safety mechanisms similar to Rust," and my point was that while they are similar in some ways, they are not as comprehensive. That's an important distinction! All of this other stuff you're talking about has nothing to do with that.
- ncmncm 7y agoWhat I see is special pleading. C++ inherits flaws from C, Rust has flaws from its late start and weaker emphasis on expressibility, both sets of flaws interfere with reliable use.