3 ms·
The important thing when breaking backwards compatability is that it can be: - automatically done - isolated within a module As long as these are true, the i
by ATsch 7y ago
The important thing when breaking backwards compatability is that it can be:
- automatically done
- isolated within a module
As long as these are true, the issues caused by breaking compatability are minimal.
It's really the Python model where it's all-or-nothing and you de-facto need to remain compatible with two releases as everyone transitions that's the problem.
- htfy96 7y ago> - isolated within a module This only exists in fairy land. In practice, mixing code from different versions is always the root of subtle bugs and ABI/API mess. For me in front of a big chunk of legacy code, I'd rather wrap them in a separate process and communicate with the remaining part through RPCs if possible.