Except D is nowhere close to stable, it only pretends to. Every
single release breaks the code. Every. Usual attitude "well, it
is a breaking change and a lot of users will be screwed, but it
is a bug fix, so we are all right?". No, you are not. I can't
imagine where such definition of "breaking" came from, it is
literally single most disastrous thing in D development process.
And I have proposed various ways to address it properly via
release process numerous times. Every single topic was ignored
both by Andrei and Walter. Because, yeah, it isn't real problem,
is it?
On Tuesday, 21 May 2013 at 21:11:36 UTC, Jonathan M Davis wrote:
We need to be willing to make breaking changes when we actually
need to make
them and avoid them when we don't. We're past the point when we
can tweak
everything to improve it. There are too many people using D now
and too many
of them wanting stability for us to continue to make minor
tweaks. Breaking
changes need to provide real value. Unfortunately, in some
cases, that means
being stuck with some things that are less than ideal, but if
we're forever
tweaking everything to improve it, we'll never be stable enough
for people to
be able to depend on us for real work.
