In C++ you can write a natural-feeling library that provides familiar arithmetic. In Rust, you will be constantly smacked in the face with lifetimes, borrowing, etc. because there's no way to do implicit clones or borrows.
Compile time reflection and metaclasses already exist as VC++ prototype, demoed at Visual C++ 2020 virtual conference.
While I enjoy using Rust, what I care about are the libraries and IDE tooling, specially for .NET and Java integrations, so for better or worse, C++ keeps being the tool to pick.
Also I have big hopes for Rust/WinRT, but it is still very early for it to eventually reach C++/CX tooling, which even C++/WinRT is currently playing catch up and where WinUI team is placing their resources.
Aside from lack of C++20 support on many targets, Clang tidy and extra analyzers require other people to take the same care as you do, an assumption that, as somebody mentioned in that article, is unreasonable to make in a non-solo project.
>Compile time reflection and metaclasses already exist as VC++ prototype, demoed at Visual C++ 2020 virtual conference.
A prototype in a Microsoft dialect of C++? That's apples and oranges.
>While I enjoy using Rust, what I care about are the libraries and IDE tooling
IDE tooling has gotten better, but of course that does still lag behind. While C++ build systems IMHO lag behind cargo, so for me that's a tie.
Conan and vcpkg are already establishing themselves, and they have a killer feature over cargo, binary dependencies.
Also too many Rust libraries still reach out to unsafe, needlessly.
To my understanding, the only reason Java was embraced with any enthusiasm in 1995 was as a way off of Microsoft's frameworks treadmill.
Better let Microsoft know about their mistake to sponsor Rust.
We don't.
I see the community quite happy with the corporate help it is receiving across the board.
Waiting to see you pushing a Rust fork, corporate free of any kind of contribution.
Any resources MS provide to improve the compiler is an obvious pure win for Rust users. Likewise, any portable code they release.
But all the code other people write that only works in MS's walled garden benefits mainly Microsoft, at the wider community's expense.
I am astonished at the need to explain this, as if the last several decades had not happened.
Plus what makes Microsoft bad, and Oracle, Apple and Google contributions good then?
I am astonished that FOSS religion keeps being a thing, while it has been proven in the last 25 years where most projects without corporate love end up.
Nobody but you has mentioned rejecting Microsoft contributions to the Rust compiler and library suite. Nobody but you has mentioned there being anything wrong with MS, GOOG, AAPL, ORCL or anybody else contributing to projects.
The topic is people who are not otherwise beholden to Microsoft (and, thus, not employed by Microsoft) writing code that works only in Microsoft execution environments.
I have explained this three times in this one thread. I don't know a way to make it any clearer. What is so hard to grasp about this distinction?
Like what? I can think of many examples where I can't express the abstraction from Rust nicely in C++. proc_macros, strong typing, macros that are part of the AST, enums with data, safe passing by reference, nice iterators (none of this begin() and end() line noise), less noisy lambda syntax, and of course memory safety.
It's especially nice abstractions where Rust shines, compared to C++.