Live data from Hacker News

My Vision of D’s Future

dlang.org

11–20 of 211 posts

Re: My Vision of D’s Future

#12
post #5
post #4

Earlier quoted context omitted.

The domain is dlang.org, the github repository is called dlang, the titles of their pages are things like "Dlang tour" and "Dlang forums". It's already searchable as dlang with no issues.

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.

I mean, Go is funded by google. So, that's kind of what you get when you use a search engine that is run by a major advertising corporation, I think.

I hold a rather controversial (at least for HN, apparently) opinion that, I don't think we can expect a corporation to be impartial if there's no legal impetus on it and there's no monetary reason for them to act impartially. Google is a business, that makes money from selling your searches and displaying advertising. So, it's going to do exactly that.

Re: My Vision of D’s Future

#13

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.

I find D easier to use than Rust or Go because of familiarity. It is very obviously C and C++ inspired but without all the sharp edges.

I also love D's metaprogramming. It feels almost like lisp. Go's lack of generics doesn't allow this and Rust's macros don't feel as comfortable for me.

Yes, D is smaller but it's also big enough for me. I don't feel like I'm missing out on much when I'm using D. If I need a library to do something that isn't already in the fairly generous stdlib, I can find it on DUB.

http://code.dlang.org/

Re: My Vision of D’s Future

#15
> Traditionally this is done by specifying data structures and RPC calls in an Interface Definition Language (IDL) then translating that to the supported languages, with a wire protocol to go along with it.

> With D, none of that is necessary. One can write the production code in D and have libraries automagically make that code callable from other languages.

If you're using an RPC IDL you explicitly do not want to share that code, you want to share that API.

Re: My Vision of D’s Future

#16
post #5
post #4

Earlier quoted context omitted.

The domain is dlang.org, the github repository is called dlang, the titles of their pages are things like "Dlang tour" and "Dlang forums". It's already searchable as dlang with no issues.

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.

I just tried and there is literally no mention of golang in any of the search results

Re: My Vision of D’s Future

#17

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.

I work in c++ and D was designed in part to address a lot of c++ complaints. so I find myself with very few issues while writing D. it's just a very enjoyable experience (subjective ik)

the meta programming is very cool also

Re: My Vision of D’s Future

#19
I have to say, I like what I read there. I'm glad they're working more on c++ interoperability. I've ported some c++ code to D before, it wasn't not too bad, it wasn't a lot of code, but it would be great to be able to work directly with c++ libraries in D similarly to C libraries.

It always makes me sad D hasn't picked up more. Usually comments I see about D seem pretty ambivalent to dismissive. It's a great language and to me has always felt like the way C++ should have been.

It does seem to be growing in popularity. Even in the years I've been using it, the number of libraries and community resources has expanded exponentially and every day new code is being added to

https://code.dlang.org/

Not to mention dub is probably the most simple straightforward build system I've worked with.

Re: My Vision of D’s Future

#20
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 was curious. The best entries for D on physical hardware:

    JSON serialization:    144 of 366
    Single query:          152 of 404
    Multiple queries:      195 of 394
    Fortunes:              154 of 371
    Data updates:          99 of 365
    Plaintext:             81 of 352
Post reply on HN