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

41–50 of 211 posts

Re: My Vision of D’s Future

#41

Post by webgoat »

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.

You speak as if you've never coded in Go before. If you've ever tried looking up information related to Go online, most of the time you'll find that results come up unrelated due to the short moniker. I've made a practice for myself to always search up "go" first and then "golang" because of how varying the search results tend to be, which leads me to also believe that much of the online knowledge related to Go tends to fall through the cracks due to bad SEO.

Re: My Vision of D’s Future

#42

Post by mhd »

thiago_fm wrote: post #11

Can somebody enlighten me, why use D when there is Rust/Go? I think on almost all cases, and also having a bigger community, it is a win for Rust/Go.

Not as exotic as Rust, due to more being in the Algol line of succession than ML's.

But boy, on the Algol-tree, it's about as far away from Go as you can, erm, go. The blog poster's predecessor was about as heavy as you can get into generics without being called Stepanov.

D tends to have quite a lot of features and lets you pick your subset, which brings it closer to languages like C++ or Scala. Go, being basically Oberon filtered through New Jersey, is a lot more minimalistic. Old Java vs. new Java, basically.

Re: My Vision of D’s Future

#43

Post by mochomocha »

dmix wrote: post #24

> We’re mostly there—using the actor model eliminates a lot of problems that would otherwise naturally occur. So D comes with an actor system baked in at the language level? I like that sort of thing after using Erlang and using some half baked libraries in other languages. I’m curious how good it is...

Yes! I've only used it minimally in a non high load scenario, but it's been a pretty smooth experience.

Re: My Vision of D’s Future

#45

Post by mochomocha »

thiago_fm wrote: post #11

Can somebody enlighten me, why use D when there is Rust/Go? I think on almost all cases, and also having a bigger community, it is a win for Rust/Go.

Compared to Rust: smoother learning curve, and you don't have to fight the compiler so much

Compared to Go: much better designed and richer language.

Obviously in terms of community, it's much smaller. But if you're ready to "build vs buy" more, or if you have some small scope project, I'd encourage you to try it.

Re: My Vision of D’s Future

#47

Post by jordigh »

ktm5j wrote: post #35

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…

I find that D is about as easy as Python to get into. Being able to use rdmd as a shebang makes D almost feel like as scripting language. A lot of Python was also pretty easy for me to directly translate into D. Here is an example:

http://inversethought.com/hg/medcouple/file/tip/medcouple.py...

http://inversethought.com/hg/medcouple/file/tip/medcouple.d#...

Re: My Vision of D’s Future

#48

Post by mochomocha »

atilaneves wrote: post #46

I didn't submit the link but I did write the blog post. AMA!

Thanks Atila! I'm curious about your work around reflection, care to give more details? This is one of the great strength of D, and having some API consolidation sounds awesome. Also: any opinion about runtime reflection capabilities? I love compile-time reflection as much as any other D user, but sometimes runtime reflection can do wonders if used parsimoniously.

Re: My Vision of D’s Future

#49

Post by StreamBright »

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.

We actually do care about those benchmarks. At a certain scale it matters how many servers you need to run a website with millions of visitors. 90% of deployments do not have this problem, yet saying nobody cares is a bit silly.

Re: My Vision of D’s Future

#50

Post by skocznymroczny »

jordigh wrote: post #47
ktm5j wrote: post #35

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…

I find that D is about as easy as Python to get into. Being able to use rdmd as a shebang makes D almost feel like as scripting language. A lot of Python was also pretty easy for me to directly translate into D. Here is an example: http://inversethought.com/hg/medcouple/file/tip/medcouple.py... http://inversethought.com/hg/medcouple/file/tip/medcouple.d#...

While I enjoy using D, I find it hard to use at times. Especially if someone isn't a C++ veteran, as soon as heavy template usage comes into play I get confused, and error messages are useless because it's several screens of errors with multiple isX() && !isY() && isZ() conditions for types.

Most of the standard library function calls return some opaque Result type which isn't obvious how to progress from. Only after some googling you'll learn that if you import std.array you can use .array() on the Result and get something usable. Oh, and I don't even know if it's possible to pass such Result to a function because you have to use auto to declare it.

Post reply on HN