Hello everyone!

Growing greatly dissatisfied with how things are in the D Programming Language, we decided it is time to fork it.
We want to change the way decisions are made, giving both more freedom to change, and more speed to decision making. We want the process of contribution to be as open-ended as possible, and not having unnecessary blockage to contributions. We also want the language to allow for faster software development. The way this is going to be achieved is still not finalized, but that is the goal.
One of the ways to achive our goal is to have core focuses of the language. Such focuses are:

• Embracing the GC and improving upon it, disregarding betterC and nogc in the process
• Concentrating on the code being @safe by default
• Revizing & rewriting the standard library, making std.v2
• Improving druntime and porting it to other platforms, like wasm
• Encouraging writing code in D, not sticking up with C
• Improving toolchain

The following stuff will be forked:

• dmd
• ldc
• phobos
• druntime

As hard as it is to say this, unfortunate code breaking changese are going to be made. But only if they help achieve the goals listed above.

The forking process is still in progress, and there isn't much done per se. We are discussing the future of the fork and what we want from it, it might be a little crazy at first. But if you wish to help out, bring your changes in, or just look around, please join our Discord server to discuss: https://discord.gg/tfT9MjA69u . Temporary website: https://dpldocs.info/opend/contribute.html

Thank you, and good luck.

On Tuesday, 2 January 2024 at 17:55:56 UTC, GrimMaple wrote:

Good luck, please use a different name for your module, not std.v2 as that should be reserved for the original dlang.

Embracing GC only sets yourself for failure

The best approach is to be pragmatic and embrace APIs around an allocator, so you can have the default allocation strategy be a GC without hurting projects that require fine tuning the allocation strategy (games, drivers, anything realtime)

type inference and tuple, that's very nice, overall the roadmap is interesting and promising, missing tagged union and allocator driven API and i would root for you

i'd make -i the default as well

but.. who is 'we'?

On Tuesday, 2 January 2024 at 17:55:56 UTC, GrimMaple wrote:

That's good news but who are "we" in this case?

The name OpenD is ok, I was thinking to naming it "D professional" but that's not so important.

This is a decision that is long overdue and I am happy that it is finally happening. It is also very unfortunate but there is simply no other way in order to progress. The important thing is that you get productive people on board who wants to contribute.

Also is there a new forum that we can use in order to discuss things? I'm talking about a forum and not a chat group.

On Tuesday, 2 January 2024 at 17:55:56 UTC, GrimMaple wrote:

Will you be breaking betterc before wasm is merged?

why both?

Got a list of names?

On Tuesday, 2 January 2024 at 17:55:56 UTC, GrimMaple wrote:

Good luck with this. I do not agree with every goal of the project but it's nice to see the community stepping up and fixing things. Maybe issue 5710 might be merged again or fixed in another way. It would be great to see async/await or some kind of stackless resumable function implemented too.

I might enter the discord later to see more about the project.

On Tuesday, 2 January 2024 at 17:55:56 UTC, GrimMaple wrote:

This alone is worth it. I pray for your success in these endeavors.

On Tuesday, 2 January 2024 at 18:54:17 UTC, IGotD- wrote:

I too am interested in this.