Evolving the D Language

[harakim]

On Friday, 7 July 2023 at 12:34:50 UTC, Hipreme wrote:
> The problem right now, from my POV, is that people such as Grim 
> is using dub dependencies. What that generates is that by the 
> default functionality being showing the deprecation messages is 
> that we need to modify unmaintained 3rd party code. How we use 
> 3rd party code right now? DUB. The problem is that dub doesn't 
> have a flag for keeping 3rd party code shut. So, in MY VIEW, 
> dub should be the one to address that problem, not the D 
> compiler itself.

I don't know how dub would address this problem by itself, but 
this is the number one issue that keeps me from using D as my 
primary personal language. And I agree that it's third party 
libraries that are an issue. I mean I have some old D1 code using 
Tango, but other than that, I do not have issues upgrading my own 
code. I don't like that it breaks, but if it were only my code 
that broke, I would use it as my primary language for personal 
projects.

After some discussion with Adam a few years ago, I heavily 
limited the libraries I use and I don't have this issue nearly as 
much anymore, but what it means is I am less likely to reach for 
D on a project, especially for something like a game where I 
would need third party libraries. And when I'm far more familiar 
with 3 other languages and tool chains, I don't reach for it for 
many of the 1-hour projects either. Although, I did do the timed 
programming course for a new job in D. :D

In short, if I could count on libraries the same as I do in C# 
and Java and, to a lesser extent, C, I wouldn't associate "new 
project in D" and "will take forever" in my mind and I would 
start by trying to make it work in D, like I used to.