Not all breaking changes are equally hurting and I disagree that you should 
strive for 0 breaking changes. In fact, most bugfixes are a potential breaking 
change, when people start relying on the bug.

Breaking changes suck and should be avoided whenever reasonable but shooting 
for 0 or near 0 breaking changes means you compromise ability to improve the 
language for all future users for the benefit of the few existing users that 
are unwilling to accommodate those breaking changes; and then you end up with 
C++ where you have to live forever with early bad decisions. 

Reply via email to