On 25/08/2018 4:00 AM, bachmeier wrote:
On Friday, 24 August 2018 at 13:04:28 UTC, Chris wrote:
For about a year I've had the feeling that D is moving too fast and
going nowhere at the same time. D has to slow down and get stable. D
is past the experimental stage. Too many people use it for real world
programming and programmers value and _need_ both stability and
consistency.
I've started moving some things to other languages myself. The problem
is that D, in its current form, has a process that is specially
optimized to make it as unusable as possible.
1. There will be no D version 3.
2. There will be no major breaking changes like autodecoding unless we
think they're important (and there are no guidelines on what's
important, just whatever comes to someone's mind on a particular day).
3. There are many trivial breaking changes made, and they can come in
any release.
4. The more releases the better.
You simply can't share a D program with anyone else. It's an endless
cycle of compiler upgrades and figuring out how to fix code that stops
compiling. It doesn't work for those of us that are busy. Why there is
not a stable branch with releases once a year is quite puzzling. (And
no, "just use the old compiler" is not an answer.)
Hmm, would a every 2 year LTS be reasonable?
We're currently doing about 1 major every 2 months now.
This can be used for boot strapping purposes too, while keeping the
number of compilers required minimal.
