Backwards compatibility is a strength, up to a point.
Backwards compatibility is a strength, up to a point.
The problem with breaking some backwards compatibility is that you just broke the ecosystem. And Python3 showed how breaking some is effectively the same as breaking all, and if you are going to do something small, you might as well do it all because its going to be a pain point for years or decades no matter how much automation tooling you build around the transition.
That is made even worse for a compiled language like C++, where if you break headers for some unsupported library it becomes effectively unusable in newer versions.
My Linux system has both installed. Software that needs one or the other just works.
I recently converted my scripts to Python3. I was shocked at how easy it was. Didn't spend more than a few minutes on any given script.
No dependencies that I need that aren't in Python3.
That point being actually having to build software that was already written.
Reminds me of C++ itself. Stroustrup posited that it needed syntactic compatibility with C. People had to be able to compile their own code with the new compiler, else his new language would never have been used.
I'm sad to admit he was probably right. He could have settled for linking compatibility, where old modules can be used from new code (and conversely). But that probably wouldn't have worked, if only because nobody wants to deal with 2 compilers and 2 slightly different languages. Also, macros and header files. Seriously K&R, what were you thinking?
Still, this is a possible path forward. To hell with syntactic compatibility, the ability to link the object files should be enough. That would at least let one use legacy libraries with the old compiler, and write the current project with the new stuff. There's just one hard part: the FFI must be seamless.