Sean Baxter not only wrote his own C++ compiler, but he authored this magnificent vision paper for the future of C++ that it moved me to reconsider my views on the safety of the language and its use future projects.

Seldom a man of my age and opinions can change his mind over something so fundamental.

Enjoy: https://github.com/seanbaxter/circle/blob/master/new-circle/README.md

circle/new-circle/README.md at master · seanbaxter/circle

The compiler is available for download. Get it! Contribute to seanbaxter/circle development by creating an account on GitHub.

GitHub

@Migueldeicaza It is really easy for people like me to think of C++ as what it was like a quarter century ago. But modern C++ and the kinds of tooling described there and elsewhere show that there is no reason to discard C++.

I still favor #Rust for new projects, but I agree that a great deal of prejudice against C++ is based on outdated assumptions.

@jpgoldberg yes, but … anyone can still write C++ in the style of 25 years ago, right? Even in a project where you’re “not supposed to,” right?
@scouten I don’t know. You can certainly build various linters into your CI.
@jpgoldberg @Migueldeicaza sure, but you’re kind of helping me make my point. People who try to portray Rust and C++ as similarly safe underestimate the difference between opting OUT of safety vs opting IN to safety. Having worked in both languages for major parts of my career, I can tell you that the difference is incredibly important.
@scouten @Migueldeicaza I want at all suggesting that they are equally safe. I do advise Rust for new projects. I was expressing relief that at least portions of the C++ community have been developing tools to move away fro the monstrosity I had envisioned based on what I’d seen 25 years ago.
@jpgoldberg @Migueldeicaza ok, then we are well aligned. Nice to have met you!