2 ms·
Breaking backwards compatibility doesn't necessarily mean bad initial design. One of the main breaks of compatibility in python 3 was making strings unicode by
by solarmist 12y ago
Breaking backwards compatibility doesn't necessarily mean bad initial design. One of the main breaks of compatibility in python 3 was making strings unicode by default. The world changes, why wouldn't a language change to meet that need?
Honestly I think a lot more languages (cough, Java, cough, cough) would benefit from breaking backward compatibility (occasionally, like every 10-15 years) rather than force it to maintain cruft that no longer makes sense to keep.