8 ms·
D is an interesting case study for good technology somehow not succeeding. The people working on it are very good and it's a really interesting language. In th
by maxxxxx 9y ago
D is an interesting case study for good technology somehow not succeeding. The people working on it are very good and it's a really interesting language. In theory it should slowly have taken over from C++ but for whatever reason this didn't happen.
- ionforce 9y agoWhat are some prevailing opinions on why it did not succeed?
- bachmeier 9y ago> why it did not succeed? Don't you mean "why it has not succeeded yet?" To some extent, I'm inclined to ask what you mean by success. It's a great language, it has three compilers, it's making progress, and it's possible to have fun writing fast, correct code quickly. It's been more successful than any other language as far as I'm concerned. Most likely you are asking why it hasn't seen widespread usage in the enterprise (like half of C++'s usage). That's a very high standard. Cost-benefit analysis usually leads to using established languages because there are benefits. D doesn't even have a very good IDE situation (I've been told), only recently got a package manager, etc.
- earenndil 9y agoEh, it only really has one compiler. DMD, LDC, and GDC all use the same frontend, they just interface to different backends (DMD, LLVM, and GCC).
- geezerjay 9y ago> Don't you mean "why it has not succeeded yet?" No, OP got it right. D had a shot at success while C++'s standardization process remained stagnant, and D could pick up the slack as it wasn't bound by backward compatibility requirements or the need to update a standard. Once ISO 14882:2011 was approved and C++'s standardization effort gathered speed, D lost the only competitive advantage and lost its chance at relevance.
- qznc 9y agoD is not dead. It is steadily growing. Not as fast as Rust for example, but still healthy. I agree that there was a nice opportunity before C++11. Now D is lurking in the shadows for another opportunity and slowly building. I believe D would be a great language for startups because it gives you options. You can do it quicky and dirty (like Python/Ruby/Perl), you can do it fast (like C/C++), you can do it safe (like Java, but not quite Rust), you can be generic and multi-paradigm (like C++), you can be easy (like Python).
- nicwilson 9y agoWhile C++ standardisation hay have gathered momentum, it still has enormous inertia (c.f static if, modules, ranges, attributes that were proposed for C++ that either failed to get in or are nowhere near as useful. I can't make do without any of those). The agility of D by by comparison is one of its greatest strengths.
- geezerjay 9y ago> While C++ standardisation hay have gathered momentum, it still has enormous inertia That's pretty much irrelevant. The last couple of standards already updated C++ so that it covered all aspects that were deal-breakers decisions on whether to pick up C++ or any alternative whose selling point was being an updated C++. After C++11 (and now C++17) no one in their right mind would decide to rewrite a whole project because of static ifs. Moreover the irrelevance of D is the only reason why it's trivial to reinvent D when it suits anyone's fancy. A committee of experts deciding on what goes into a standard is not the same as a developer deciding on a whim on what he might implement next. If D was relevant and it's adoption motivated an ISO standard to coordinate which features went into any implementation then I seriously doubt that it would do better than C++.
- systems 9y agoI would strongly recommend you browse and maybe contribute in the Dlang forum https://forum.dlang.org/ https://forum.dlang.org/ , to build your own opinion, the forum is very friendly and welcoming for beginners Some of the prevailing opinions on why D didn't succeed - Garbage collection, D has a GC, and for a very long time it seem to have been positioning itself as a C++ replacement, having a GC, seem to have hurt D more than it benefited it, in this regard - D vs D2, the current Dlang is actually as I understand D2, moving to a new version that is not fully backward compatible seem to have at least in the past scared away some possible adopters, this seem to be no longer the case, there is only one D now, and this might be a case when lack of popularity was helpful - licensing issues, I really dont know much about this, but there was some licensing issue surrounding the main D lang implementation DMD, which was also resolved recently The above 3 points, are what I would call the "prevailing opinions" Two of them are now fully resolved and only the first one GC , is a work in progress ... once its resolved, and it seems they are working on it ... there will be no excuses What I personally believe, after lurking in their forum for a while - D, doesnt have a good product owner, it lacks vision, and it have no competitive advantage - Walter Bright and Andrei Alexandrescu, are super smart developers, but in my humble opinion ... very bad Product Owners, and just to support my opinion, before anyone gets angry at me ... we all agree D is not popular, so ... this is just a statement of the obvious - Strategic advantage is a key word here, D have none, and again, the Strategic is a key word here, even if some will list for you the advantages of D, none of them is Strategic With all I have said, dont let this stop from learning D, I do plan to learn more of it, and while I don't see D taking over from C++, Go, OCaml or Python ... I think it might be a good tool for small teams, who don't want to be fragmented across many languages
- le-mark 9y agoTo me it seems like there are three broad categories of applications one would use D to implement; network services (ie servers), gui apps, and "other" such as compilers or command line tools. IMO go has won for writing servers; it's incredibly compelling, it has it all (except generics, as someone will surely interject); crypto, ships with easy to use protocol impls (ie http, websocket, etc). The gui lib story for D isn't clear to me at all. Are there bindings to gkt or qt for example? Maybe someone can respond here about that. That leaves "other" which, sure, D seems like a great option.
- uvtc 9y agoI think a big part was the licensing issue. Before April 2017, the official compiler back-end was some non-open-source license (dunno which). In this day and age I couldn't see using a compiler that wasn't free software. But now that's been fixed --- the reference compiler is now all Boost licensed, and GDC (the GCC front-end) has even been officially accepted into GCC (woot!). Also, I'm not sure how long the standard package repository and module installer (dub) has been around. But that's here now too. I think the future of D looks very bright. I'm still learning, but to me D seems somewhat similar to Python, except: * it's compiled to native code instead of interpreted * it's syntax uses curlies/semis instead of whitespace * it's statically typed (but has type inference so you can type many variables as just "auto" and the type is inferred) * it has [dub](https://code.dlang.org/ https://code.dlang.org/) instead of the [cheeseshop](https://cheeseshop.python.org https://cheeseshop.python.org) (of course, the cheeseshop is currently much larger) Anyhow, very much enjoying D so far. :) I expect D's popularity to grow as more people desire a statically-typed, compiled language, with the convenience of a GC and easy access to native (C) libraries.
- qznc 9y agoI think about that sometimes. I do not believe that it is really a technical problem. While there are arguments to be made (not safe by default, garbage collection, lacking IDE support, ...) these are not killer arguments. In many cases, D has more advantages than disadvantages. Lack of manpower is a problem. Only Walter Bright and Andrei Alexandrescu work full-time on D. The rest is volunteers. This means development proceeds very slowly compared to Go or Rust. On the other hand, maybe it is more a symptom than the problem. Perception is a big part. Even in this discussion you can see people remember the "dual standard library problem" which was solved a decade ago. Maybe D just needs a good PR team.
- stepik777 9y agoMaybe it is just not a good technology. Just compare it to others: C++ - memory unsafe, no GC. Java - memory safe (by default), has GC. Rust - memory safe (by default), no GC. D - memory unsafe (by default), has GC. Authors of Java solved memory safety by adding garbage collector. Authors of Rust managed to make memory safe language without GC while authors of D made a language with GC that is still memory unsafe.
- 52-6F-62 9y agoIt would be a little more accurate to say that in D, memory safety is optional. If you wrote every method using the @safe flag, you'd be forced to write a memory-safe program. Eg: void main() @safe { int everything = 42; int* theAnswer = &a; int* earth = theAnswer * 2; // Won't compile. } With no flag or @system, safety is not ensured. Using @trusted will allow a function to be called, safe or not, from other safe functions ending the safety. But by design @safe functions can only call other @safe functions.
- qznc 9y agoYes, D picked the wrong default. That is just a minor annoyance though. Add "@safe:" to the top of all source files. Check for that in your CI. You are safe now. The advantage is that you ignore the issue initially. No fighting the type system like in Rust, but easy coding like in Python. Later, when you need your code to be reliable, add annotations and fix problems with compiler guidance.
- katastic 9y agoThe reason D isn't popular is simple and not a fault of the language itself. It's one of marketting. - Go is backed by Google. - Rust is backed by Mozilla. - C# is backed my Microsoft. - D is backed by... D users... and the two language architects. A few schools use it. A few companies use it.(::cough::This little company called Facebook::Cough::) The other is target market. D appeals to a new, or more advanced kind of programmer. A new niche or category. A programmer that doesn't get produced at most colleges, or demanded by most companies. And if they're not produced or demanded, that category isn't going to fill up with programmers. Nobody would have used Java if schools across the nation didn't tell kids that "Java was cool" and the JVM wasn't something to be afraid of. There are categories of programmers. No one can say that a LISP programmer is quite like a C programmer. - C programmers want "nicer assembler." C. - C++ programmers don't want a GC. (Though D is working toward a GC-less standard lib.) - Python/Java/C# programmers are (more likely to be) afraid of systems languages that can segfault like crazy if you don't know what you're doing. D appeals to programmers who aren't afraid of the entire stack. They write, understand or at least appreciate assembler and caches, while also dabble in high-level templates and functional programming. I can absolutely say I've grown as a programmer after looking through D features and going, "Why don't I know how that works?" The guys behind D are brilliant, and professional. Watch any of their talks. Andrei Alexandrescu works for Facebook and still writes plenty of C++. He also wrote THE quintessential "Modern C++ Design" book on template meta-programming. And Walter Bright has been writing compilers for decades. This is not a toy language. Here's plenty of benchmarks showing D as fast as (and sometimes beating) C/C++ _and_ having low memory usage. https://github.com/kostya/benchmarks https://github.com/kostya/benchmarks Meanwhile, the benchmark is misleading. Because not only is generally as fast as C/C++, but it's way more productive to write in. But back to adoption. It's simple. 1) No corporate backers pushing it, 2) A language for advanced/multi-talented programmers is either scary or "unnecessary" to single-talented programmers. Most C programmers are afraid of, or think templates are unnecessary. Most C++ programmers are afraid of a garbage collector (even if it's a completely deterministic one that only fires off during specific allocation points). As a mostly C++ programmer, I was apprehensive of D's GC. But the more I read, the more confident I've been, and, I've had zero actual problems with it. I'm pushing 130 FPS on my netbook just fine, and because D isn't a toy language, I can easily move to static pools and have zero GC allocations.