Earlier quoted context omitted.
I think the fundamental problem with D is much simpler than that, it's the technical context. D is a better C++, but it's not better enough to escape the gravitational pull of C++. Rust is sufficiently compelling, with its focus on memory safety.
I keep saying this and having the exact same argument with everyone every single time I mention it (and I'm sure here we'll go again), but D's fundamental problem was its GC. Its mere presence colors the code that uses it, and once your dependencies use the GC, you have no recourse. It's impossible to abstract away. I fail to see how such a language could ever substitute for C++.
OpenD, a D language fork that is open to your contributions
91–100 of 322 posts
Re: OpenD, a D language fork that is open to your contributions
#92My suggestions: completely get rid of GC(use refcounts or borrowed pointers), add macros(see FreeBasic extensions of C macros), migrate everything complex/optional out of stdlib to specific packages(Rust ecosystem is centered on packages not stdlib), and you will have a solid competitor to C++ and perhaps Rust. Rust of course has better macros and type system, but D looks simpler and more approachable for rapid proto…
Re: OpenD, a D language fork that is open to your contributions
#93My suggestions: completely get rid of GC(use refcounts or borrowed pointers), add macros(see FreeBasic extensions of C macros), migrate everything complex/optional out of stdlib to specific packages(Rust ecosystem is centered on packages not stdlib), and you will have a solid competitor to C++ and perhaps Rust. Rust of course has better macros and type system, but D looks simpler and more approachable for rapid proto…
Your suggestions are moving backward, and GC by default and no macro made D intuitive and Pythonic that are big plus in any modern programming language construct. The non GC is not really needed unless you're working on OS control primitives but again D give you alternative unlike Go. Every modern languages should avoid macro like a plaque otherwise you will sooner or later create a ghetto inside your community not u…
Re: OpenD, a D language fork that is open to your contributions
#94Earlier quoted context omitted.
Let's call it E.
E, F, G, and H are already taken. It's hard to say whether I is available, or un-googleable. J through W are also taken. X++ is taken, but X seems to be available. Y and Z are taken. A would be an excellent choice were it not completely un-googleable. Finally, B is a famous precursor to C.
APL is named after the book A Programming Language
Re: OpenD, a D language fork that is open to your contributions
#95D is such a sad case of how a good technical product can fail due to poor leadership and decision making. A language is more than just a compiler, it's also an ecosystem and a community. D's community is actually very welcoming but man, watch some of the DConf videos and Q&As on Youtube and it's cringe seeing key leaders talking down to people, or dismissing people's concerns, or just have this ego about themselves l…
The thing that moved me away from it was a lack of purpose, which isn't exactly how I would have put it at the time, but in hindsight seems obvious.
The way in which I'm certain that this is true is that if you had the leads try to create a Venn diagram of what the project does and what is central to it vs periphery, they would fail to agree. And if they fail to do that, they will fail to coordinate on the features. And that creates the stagnation and difficulty with contributions.
As well, the reason why that failure leads to a retreat into technical digression - which I know happens out of personal experience - is because that deflects questions by adding scope. It promises an escape from the confrontation: "if I just accumulate more work, it will all come together someday". The problem is that adding scope doesn't solve the contradictions that made you retreat in the first place, it can actually deepen them by creating sunk costs. It's a bad adaptation to the challenge.
If we compare it with, for example, the Niklaus Wirth approach, he would have the Venn diagram completely clear in his mind before committing to any real implementation. And therefore the language would do exactly what he wanted it to do, and it wouldn't need to be scoped into a 20-year project. Thus, he made many languages during his life, mostly of a similar flavor, but with a clear intent of adding something specific that he hadn't covered before.
Re: OpenD, a D language fork that is open to your contributions
#96Re: OpenD, a D language fork that is open to your contributions
#97Earlier quoted context omitted.
E, F, G, and H are already taken. It's hard to say whether I is available, or un-googleable. J through W are also taken. X++ is taken, but X seems to be available. Y and Z are taken. A would be an excellent choice were it not completely un-googleable. Finally, B is a famous precursor to C.
> A would be an excellent choice were it not completely un-googleable. APL is named after the book A Programming Language
Re: OpenD, a D language fork that is open to your contributions
#98Follow up post: https://dpldocs.info/this-week-in-d/Blog.Posted_2024_01_08.h...
> Again, remember, I have other work and responsibilities, so I can't do a great deal of work myself, even if I wanted to.
Re: OpenD, a D language fork that is open to your contributions
#99D is such a sad case of how a good technical product can fail due to poor leadership and decision making. A language is more than just a compiler, it's also an ecosystem and a community. D's community is actually very welcoming but man, watch some of the DConf videos and Q&As on Youtube and it's cringe seeing key leaders talking down to people, or dismissing people's concerns, or just have this ego about themselves l…
If you're put off by key leaders talking down to people, I think you'll want to spend some time in Nim's forum and issue tracker before considering it as an alternative. (YMMV, of course, but I was put off by what I found.)
Re: OpenD, a D language fork that is open to your contributions
#100Earlier quoted context omitted.
Let's call it E.
E, F, G, and H are already taken. It's hard to say whether I is available, or un-googleable. J through W are also taken. X++ is taken, but X seems to be available. Y and Z are taken. A would be an excellent choice were it not completely un-googleable. Finally, B is a famous precursor to C.