Question to the core team. Whats the plan and roadmap for D ?
a. are we planning to keep D just as a hobby language or a real contender for industry use. Despite being complex, rust has started to get adopted in industries. Whats our plan ?

b. When are we planning to focus on memory safety and use that as our strength

c. Will we ever make D as both a GC and non GC language. So that it can be used across control plane, data plane, kernel. I know betterC, but could we make it more easy and accessible common public to able to use phobos. I know people say 95% is done etc.

d. Why there are no working groups for tooling, webframeworks, performance, compiler etc so that we can improve on each area.

e. Why is weka not sponsoring ? why are we not advertising that the fastest filesystem is made in D ?

f. D has all properties to make it a good language. But needs more work and marketing. Why cant we make D as a safe and fast extension to C++ & python

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

No, because D has painted itself into a corner. Not only between GC and manual memory management but also that you cannot swap GC types (any type of GC, like Nim can) because D treats all pointers the same. That might have some advantages but I would say that the disadvantage is huge.

Memory management wise, D is going nowhere as it seems.

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

D can already be used professionally

How are we not?

Is there any language more flexible than D in this regard? You already have much choice.

This is a valid point but the answer is how would that be done.

Can't answer this. It's a bit weird yes.

You are correct sir, we must market D more. Do your part and spread it ☀️

D The biggest problem is that there is no direction.
Moreover, D author never confronts users' questions directly.
D needs to be organized and, at the same time, have a clear goal.
Let users, beginners, know what you're going to do.

However, the D authors and leading developers have never faced this problem.
If the user doesn't know what you're trying to accomplish, no matter how good the language,
The user had to leave. Because we don't know the solid point of your language.
What are you going to do? Are you going to match the user's expectations?
Can users see the improvement?
Yes, small progress is everywhere. But what we expect is your clear goals and steps.
C + + has 20, 23 and 26,
Rust, many companies are using. Go, even if itaims at junk template.
But what's D's goal? Do we have a schedule?

Is it true that we are doing things at random, and whoever has good things ,and then we will copy it?
Hope, D writers, wake up and make a schedule.
Let users see hope.

Well, suppose I'm the leader of D
0, do a vote, bull force people, important library author, vote for 10, ordinary users, vote for 1, first investigate, understand the different needs of various users

1. Focus on users' core requirements, such as' better c ', such as' memory security', such as' various bugs fix', such as' C 'compatibility, and' C + + 'compatibility.

2. Gather a group of enthusiasts and experts together to understand their respective areas of expertise, and assign corresponding tasks in their respective areas. At the same time, ask them to give a timetable for completion. Of course, there are rewards

3. Allocation of money: 1,50% for publicity. 2,50% for reward for accomplishing the above tasks. At present, there are too few publicity and too few reward, so efforts must be made in this regard. At the same time, money should be allocated according to the stage change

4. Action

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

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 begining ov dlang v2 it was : it is not our faut the War tango vs photos as stdlib just broke our community. We need a killer application à la Ruby on rails.
Now it is not 1 killer application but a set of software environnements on se, Big data, sécurité, gui, games...
How they Can Do it?
To remember D is bien in 2001 and Rust ...

Instead to add New feature maybe waste dôme Time on one of previous topic des robes 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 ...