It seems like there is no plan nor roadmap. It's really hard to invest your time into something, realizing there is no team that works on fixing issues and adding features. Right now it's easier to stuck with C++. Maybe it's not fun to use it, but at least it's thought out, stable, has a large code base, tooling, and the most important, it has a roadmap. D needs dictatorship until it gets rid of the most annoying issues. Somebody has to make unpopular decisions.

On Thursday, 13 May 2021 at 20:57:13 UTC, dogman wrote:

We used to have vision documents[1] but I believe they were stopped since they never really led to anything.

I miss them :(

[1] https://wiki.dlang.org/Category:Vision_Statements

On Friday, 14 May 2021 at 23:05:38 UTC, SealabJaster wrote:

The latest of the sort (Still pretty old):
https://dlang.org/blog/2019/10/15/my-vision-of-ds-future/

On Thursday, 13 May 2021 at 20:57:13 UTC, dogman wrote:

The plan is for the D community to whine and moan as they wait for Walter to improve the VS Code extension or write web frameworks.

The only important difference between D and languages like Rust, Go, and Python is that those languages developed communities of developers that got stuff done, whereas D didn't. Since D's community is so ineffective, it's unlikely we'll ever see widespread D adoption.

On Friday, 14 May 2021 at 21:29:59 UTC, bioinfornatics wrote:

Sorry I wrote from my phone and my spellchecker has done some weird job.

So I rephrase:

Do not plan to get an answer

This kind of question is asked every years since at least 10
years ago.

I am remind that at beginning of dlang v2 it was :
«it is not our fault, the war tango vs photos as stdlib just broke our
community. We need a killer application à la Ruby on rails.»

Now it is not one killer application but a set of software
environments on web, Big data, security, gui, games...
How they Can Do it, in 10 years we didn't get a killer application so a set …?

To remember D is born in 2001 and Rust ...

Instead, to add new features … maybe would b a good idea to waste some time on one of
previous topic describe above in order to get a chance to be more heavily used...

I remember a time to where Facebook use D to replace c++ code
but now ...

On Saturday, 15 May 2021 at 15:05:44 UTC, bachmeier wrote:

That's not true. Those languages are very focused in their feature set, and have polished their main feature so that that feature is objectively "best in class".

D has over time had many sub communities that has created significant frameworks (in terms of scope and effort). Some went off to create their own language... That is just facts.

On Saturday, 15 May 2021 at 15:05:44 UTC, bachmeier wrote:

This is not true, that is, its not the only difference. More important difference is that Python and Go never said "GC is too slow and inappropriate in some situations, we should offer complete support for some other way of managing memory", while Rust never said "Borrow checker is too annoying and GC is really convenient in some situations, lets implement memory barriers and stuff". They chose their way of dealing with it and just improved it over time without changing course.

On Sunday, 16 May 2021 at 03:01:55 UTC, nkm1 wrote:

Many people has put a significant effort into the D GC, but where D differs is in being C-like (Go is not C-like although they may claim it is) which isn't GC friendly.

The fact that dmd does not ship with GC enabled speaks volumes...

On Sunday, 16 May 2021 at 03:46:50 UTC, Ola Fosheim Grostad wrote:

Hardly. dmd doesn't release memory, either. Does that "speak volumes" about free? Neither is suitable for Walter's performance goals with dmd. That's precisely why D allows you to disable or avoid the GC when you need to.

On Sunday, 16 May 2021 at 03:58:15 UTC, Mike Parker wrote:

A global bump allocator is just another word for a memory leak. You dont need a comp sci degree to understand that this is not a good "feature".