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 He kind of missed me first thing out the gate by omitting a fifth key attribute of successor languages: package management. This isn’t even new; Python, Ruby, and Perl have had this for decades (CPAN turns 30 this year!), and they’re core to Rust and Go. Integrating C++ libraries remains a time-consuming and error-prone ritual, and keeping up to date is a huge point of friction. I dread nothing more about going back to C++ than external dependencies.