Goals and Priorities for C++

Re:Goals and Priorities for C++ by mianos on Thursday May 21, 2020 @08:56PM (#23267574)

Not to be negative but this reminds me of Python 3, where they want to make a largely but not completely compatible new C++. Like Python 3, it would be great to get a bunch of things fixed and force people to use the new, better, way of doing things. But, this comes with complications.

I am a C++ and Python developer. I did C++ for 20 years then python for 9, then C++14/17 for 3. I really like the new C++ and think it could be made into a better language while still retaining the deterministic performance.

What we don't want is Python 2 to Python 3 situation. That might mean calling it a new language.

[ Parent | on HN ]

Re:Goals and Priorities for C++ by Pxtl on Thursday May 21, 2020 @10:49PM (#23268239)

Honestly, I think python 3 broke too little. I mean, if you're going to break backwards compatibility, make it worth it. That should've been the time to lock down the language enough that PyPy and other non-cpython interpreters could finally thrive.

[ Parent | on HN ]

Re:Goals and Priorities for C++ by CJefferson on Friday May 22, 2020 @03:42AM (#23269597)

I agree. They changed 'print', which broke basically every non-trivial program ever written, but then didn't clean up so many other smaller issues.

[ Parent | on HN ]

Re:Goals and Priorities for C++ by dman on Friday May 22, 2020 @03:29AM (#23269532)

Could not agree with you more.

[ Parent | on HN ]