Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My Vision of D’s Future

dlang.org

Post reply on HN
Print view View original

31–40 of 211 posts

Re: My Vision of D’s Future

#31

Post by bsaul »

coldtea wrote: post #25
kitd wrote: post #6

D needs to up its game with the Techempower benchmarks IMHO. Vibe.d has been completely left behind by the usual Rust/Go/Java suspects. I'm very confident that it is capable, but that isn't particularly obvious atm.

I don't think anybody really cares about the Techempower benchmarks. Else we'd all be using Vert.x or so. The most popular frameworks having the 90% of deployments, are at the middle to bottom of the Techempower benchmarks.

I think people thinking about using D care a lot about benchmarks. The reason "most popular frameworks" are in the middle to bottom of the list is becaue they are made with dynamic languages which are/were very popular for ease and speed of development, with a huge number of web-programming functions baked in.

On the other hand, you will note that go / rust and C frameworks (which are playing in the same field as D) are on the top of that list.

Re: My Vision of D’s Future

#32

Post by littlestymaar »

beat wrote: post #9
jacobush wrote: post #3

As long as we search for stuff on the internet with text terms (i.e. Google ) you've got to enhance the name of the language. If only something boring as DLang, please please do this. I feel bouts of sympathy every time I think of D, and I'm not even a hard core fan or anything. No need to change the logo or anything. Just sneak in something actually searchable ( dlang , or whatever ) in footers and headers of docume…

Yes, this is why the Go language was a complete failure too. And C before that.

Tbf, C was big way before Google even existed (and nobody expects "Clang" to mean C, unlike D or Go). And even if it obviously didn't cause Go to fail, it's still something annoying when googling up about Go, because "Golang" doesn't always work.

Re: My Vision of D’s Future

#33

Post by Profan »

I wish standardizing documentation tooling (everyone uses a different tool today and ddoc by default has _no_ styling, no navigation, no nothing, so usually nobody writes docs for their code unless it's a big project like vibe.d) and IDE support was on this list (vscode centric tools exist and mostly work, but it's still fairly hit and miss) .. D's tooling has languished for a long time even if it is a great language otherwise.

Re: My Vision of D’s Future

#35

Post by ktm5j »

As someone who has only somewhat recently started using D, I would love to see this language succeed. It's been such a pleasure to use.. scope guards, string mixin, inline json & std.json. It's been so useful for the code I write at work. Much love for D

The one thing I would add to this list is documentation! There is a lot of good documentation available, but not for everything you would expect. For example, I had a hard time figuring out the behavior of sub-packages within a dub package. Some more explicit documentation on this subject would have been appreciated.

Re: My Vision of D’s Future

#36

Post by furyofantares »

rickette wrote: post #10
jacobush wrote: post #3

As long as we search for stuff on the internet with text terms (i.e. Google ) you've got to enhance the name of the language. If only something boring as DLang, please please do this. I feel bouts of sympathy every time I think of D, and I'm not even a hard core fan or anything. No need to change the logo or anything. Just sneak in something actually searchable ( dlang , or whatever ) in footers and headers of docume…

It's beyond me why most languages fall into this trap: C, C++, C#, D, Go, etc. All hard to search for. Granted some of these predate the internet, but most do not. Almost looks like some kind of secret agreement between language designers.

I’ve used all of those languages and never had a problem searching for things for any of them, with the exception of C# very briefly at the time it was released.

Whenever this complaint is lodged I feel like it’s just an easy thing to complain about that isn’t an actual problem at all. Am I wrong?

Re: My Vision of D’s Future

#37

Post by mhd »

What about -betterC? I always thought this was a nice "pivot" for D. It would be great to have more support for this direction. You can't avoid malloc there, but maybe some instrumenting for leak detection or some libc replacements that exploit or are exploited by the language.

Other than that, I'm okay with anything that was already in Eiffel or Modula-3…

Re: My Vision of D’s Future

#38

Post by karussell »

kernyan wrote: post #30

>I think we need a ridiculously fast interpreter so that we can skip machine code generation and linking. To me, this should be the default way of running unittest blocks for faster feedback, with programmers only compiling their code for runtime performance and/or to ship binaries to final users. This would also enable a REPL. I am most excited about this, where a language supports two modes 1) interpreter for devel…

Java can do this via AOT or partially also JIT compilation.

For AOT there is this JEP: https://openjdk.java.net/jeps/295 and a different project: the GraalVM

Re: My Vision of D’s Future

#39

Post by [deleted] »

coldtea wrote: post #26
arunc wrote: post #5

Earlier quoted context omitted.

The sad part is, every time I type dlang in google for something, it tries to correct it to golang and that's terrible. duckduckgo doesn't do that.

> every time I type dlang in google for something, it tries to correct it to golang and that's terrible Doesn't do it at all to me...

[deleted]

Re: My Vision of D’s Future

#40

Post by scns »

kernyan wrote: post #30

>I think we need a ridiculously fast interpreter so that we can skip machine code generation and linking. To me, this should be the default way of running unittest blocks for faster feedback, with programmers only compiling their code for runtime performance and/or to ship binaries to final users. This would also enable a REPL. I am most excited about this, where a language supports two modes 1) interpreter for devel…

OCaml works like that
Post reply on HN