On Monday, 22 May 2017 at 21:08:02 UTC, Jolly James wrote:
On Monday, 22 May 2017 at 07:28:23 UTC, Vladimir Panteleev
wrote:
On Sunday, 21 May 2017 at 22:47:44 UTC, Jolly James wrote:
On Monday, 1 May 2017 at 18:30:53 UTC, Rainer Schuetze wrote:
Please note that the next dmd installer will also detect
VS2017 and setup directories correctly in sc.ini:
https://github.com/dlang/installer/pull/227
I really like this philosophy:
"It does not work, a fix is available, but it won't be rolled
out (for now). Who cares about those who cannot use the
broken software?"
Please don't antagonize volunteer contributors who are
actually creating and improving things. We have a release
process for a reason, we can't ship every single change
immediately. If you require a solution urgently, use a
workaround or build it from source yourself.
My message was neither addressed directly to anybody of the
volunteer contributors (I have a huge respect of them and their
great work), nor to anyone at the D Foundation directly. I just
wanted to critize the whole release cycle stuff itself.
I mean, if for any circumstance, e.g. like the VS2017 thing
(which did not suddenly appear from one day to another anyway),
the whole software cannot be used without larger fiddling (in
this case: setting up NSIS + plugins), it seems quite strange
to not simply update the installer, which would be a work for a
few minutes - and after that everybody would be happy.
But to be honest, I don't think that this is a problem of D.
More or less, this is something that appears everywhere in the
world of open-source. Here it annoys and chases away users, in
the corporate sector you could not do so, as this would cause
the company's ruin.
We already have nightly builds for all platforms supported by dmd
[0]. We just need a nightly build of the installer, in addition
to the 7zip archive for Windows. So I'd say we're already doing
much better than 1-2 years ago.
[0]: http://nightlies.dlang.org/dmd-master-2017-05-23/
