Dicebot on leaving D: It is anarchy driven development in all its glory.

[Chris]

On Wednesday, 22 August 2018 at 11:59:37 UTC, Paolo Invernizzi 
wrote:
> Just found by chance, if someone is interested [1] [2].
>
> /Paolo
>
> [1] 
> https://gitlab.com/mihails.strasuns/blog/blob/master/articles/on_leaving_d.md
> [2] 
> https://blog.mist.global/articles/My_concerns_about_D_programming_language.html

Two things:

1. from the blog "You can't assume that next compiler upgrade 
won't
suddenly break your project or any of its transitive 
dependencies."

2. it took till 2018 to fix this: 
https://issues.dlang.org/show_bug.cgi?id=16739

As to 1.: this is my biggest fear and chagrin: with every new 
version my code might break. And new versions come quite 
frequently. Having to spend time fixing what wasn't broke a week 
ago is a nightmare.

As to 2: just keeps you from writing code

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 been working with Java recently and although it is not an 
exciting language, it does the job and it does it well. You can 
rely on it to get the job done - and get it done fast. And you 
know that your code will still work next week, month or in 5 
years. In everyday programming life you don't care about the 
latest fancy features. Imo, D should slow down, take inventory, 
do some spring cleaning and work on useful libraries and a sound 
ecosystem. I don't care what color the bike shed is as long as 
there are bikes in there that actually work.

Atm, I'm not considering D for any important and or big projects.