5 ms·

Not that I am not agree with the link but Python is not caveats free either. The fact that they have to "fix" the language in one version making it incompatibl

• 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.
• Walkman 12y ago
  There was no desperate need for Unicode everywhere when Python 2 was made. Looking back it's a fix, but other languages have this problem either and can't really be avoided.
• Demiurge 12y ago
  The smell of perfection trying best good is the smell I want to wake up to every morning.