Live data from Hacker News

Why I Like D

aradaelli.com

131–134 of 134 posts

Re: Why I Like D

#131
post #99
post #89

Earlier quoted context omitted.

I don't disagree that it can be useful (eg. from one of the other projects mentioned in the thread: https://github.com/Netflix/vectorflow/blob/master/src/vector... ), and I definitely saw plenty of people that liked it. I think it existed in the same realm as a feature like lisp macros which are incredibly useful but when overused can turn the code into an inscrutable mess. The question for me was always how much the…

> b!(c.d)(a) The template parameter after a ! without parentheses is always 1 token, so it's never one of the first two interpretations. Furthermore, the point is that often when writing generic code, you're not supposed to care what the `.d` means specifically. For example, an `InputRange` is defined to have `.front`, `.empty` and `.popFront` properties. Is `.empty` a member variable, function, or constant? Doesn't…

The trick is, most newcomers aren't just bothered by auto and would like the explicit type here. What they want to do is actually pass that output into another method. And in that method they need to know the type. I mean, you could accept input range in the method, but then you are losing some typing information.

Re: Why I Like D

#132
post #18

Yes, I just wished more people liked D so it got momentum.

I first learned C++ 20+ years ago. While I've appreciated it, I also knew its shortcomings and had been looking for a replacement. D had some missteps along the way that lost some initial traction. I also wouldn't be surprised if timing was a factor with more C++ warts being added while the programming community has learned more lessons along the way that could be applied to the next languages (Go, Rust). As I follow…

Ironically as someone who wishes D distanced itself from C++ more, my feeling is that D is catering too much to the C++ programmers and not catering to the "Java programmers" enough. There is a lot of effort going into not only binding to C/C++ libraries, but also C/C++ interop, which appeals to a small group of users who potentially want to migrate a C++ project into D incrementally.

Re: Why I Like D

#133
post #129

Earlier quoted context omitted.

Yeah I do much in C# and almost never use generics. And when I do it is almost always not what I want. D has me fooled and I can't imagine Go choosing to go further in D's direction over C#. I feel sorry for them.

You almost never use List ? Dictionary ? IEnumerable ?

Those don't matter, because while you can't build your own in Go, the built in types provide the same functionality.

Re: Why I Like D

#134

Earlier quoted context omitted.

I was puzzled by strange linguistic ideas of go's designers. The reference to the English language can't justify go's syntax.

Do you have an example top of mind?

Array of bytes []byte being English, but byte array byte[] being not English.
Post reply on HN