Live data from Hacker News

D 2.069.0 released, compiler automatically ported from C++ to D

dlang.org

101–110 of 131 posts

Re: D 2.069.0 released, compiler automatically ported from C++ to D

#101

Earlier quoted context omitted.

Some things D has that Rust doesn't: compiler-checked function purity annotations, higher-kinded types, variadic functions/generics, types parameterised by numbers, compile-time function evaluation, mixins, a fast compiler (the reference DMD compiler), powerful and convenient compile-time reflection (I think technically Rust can do anything D can at compile time, but it requires writing a syntax extension to do so).…

> higher-kinded types Well, not really. Higher-kinded type parameters are something that requires a kind (typeclass) system in the first place, which D intentionally doesn't have (as D's authors are opposed in principle).

kinds and typeclasses are rather different, are they not?

Re: D 2.069.0 released, compiler automatically ported from C++ to D

#102
post #93

Earlier quoted context omitted.

Since 1.0 last May, we have a strong commitment to backwards compatibility as well. Stability should not be an issue any longer.

My impression is that things are settling down now, but I've encountered quite a few rust code bases that required "latest rust" (latest > 1.0) - and even "nightly". Not to say that rust-the-language hasn't stabilized, but I think the point about D being (way) more mature still stands? (Note, it's a good thing that people are writing code to test/work with/exercise latest rust/nightly etc -- but just because I can be…

Yeah, I mean, I don't take this as a critique, it's the same for basically every language. When you build a project with a new version, you might take advantage of the new features. Such is life. :)

Re: D 2.069.0 released, compiler automatically ported from C++ to D

#103
post #66

Earlier quoted context omitted.

As someone who's been following the hype, but not really jumped on yet, the difference (whether real or imagined) seems to be that rust is trying to do something new , and D looks to be (and I've seen it aggressively marketed as) C++ with some better choices and cool features. Personally, I'm not really interested in C++, but I am interested in getting for familiar with a systems language, so rust interests me.

From what I understand, the only new thing Rust is contributing is managed lifetimes. Everything else is, like in D, just borrowed from other languages and put together. That said, I've mostly heard that lifetimes are still too young to be worth the trouble. So the one new thing Rust does bring to the table isn't really ready yet.

  > lifetimes are still too young
While some stuff is new, the core of the idea goes back to Cyclone in 2001.

Re: D 2.069.0 released, compiler automatically ported from C++ to D

#104

Earlier quoted context omitted.

Rust inherited the enthusiasm of some very prominent and outspoken members of the Ruby community. These ex-Rubyists honed the craft of projecting excitement with Ruby and RoR, and brought these skills and talents with them when they moved to the Rust camp. The D camp hasn't really had anyone like that join them.

I have to agree on this. I was surprised to see that a majority of the Rust community actually comes from some web-development domains. Especially when comparing Ruby, a highly flexible dynamic language, to Rust a language full of constraints (for its own valid reasons). Note that the a hype train is a two-edged sword, it will both bring a strong community and might also induce a cliff with the other communities (pra…

As someone who fits this mould, for me, it's not exactly that. Yes, in my professional life, people know me for my Rails work, but I learned C at a very young age, and while my systems-level stuff was a bit out of practice, for me, Rust is a _return_ to the kind of stuff I used to do earlier in life.

Oh, and I'm not sure "majority" is really true. Yeah, maybe some of us have disproportionate impact, but a very large number of people in Rust-land really know their systems stuff. I am humbled to work alongside such talented people.

Re: D 2.069.0 released, compiler automatically ported from C++ to D

#105
post #26

D is a really amazing language that manages to correct the mistakes of c++ but still retain its good parts. it's a shame that it's not more popular.

I often wonder if it were released today as "new" if it would of gained plenty of more hype. One thing I think that Go has that D is lacking is the standard library. With Go you can write a web server, a mail server, and plenty of things right away out of the box. Where in D and other lovely languages you either need to get a package manager, or make your own. Outside of this small detail I think D is amazing at what…

There's the dub package manager for D. http://code.dlang.org/

I don't think I'd want web and mail servers straight into the standard library out of the box. Those are way too specific. For example, there's already vibe.d for web servers and its doing an excellent job. They even have compile-time HTML templates!

As for IDEs, on Windows I've recently used VisualD and it did a good job. It's not yet as complete as the C# integration of Visual Studio (especially when taking ReSharper into account), but it definitely feels like an IDE. It already has improved hugely over when I last used it last year.

Re: D 2.069.0 released, compiler automatically ported from C++ to D

#106
post #66

Earlier quoted context omitted.

As someone who's been following the hype, but not really jumped on yet, the difference (whether real or imagined) seems to be that rust is trying to do something new , and D looks to be (and I've seen it aggressively marketed as) C++ with some better choices and cool features. Personally, I'm not really interested in C++, but I am interested in getting for familiar with a systems language, so rust interests me.

From what I understand, the only new thing Rust is contributing is managed lifetimes. Everything else is, like in D, just borrowed from other languages and put together. That said, I've mostly heard that lifetimes are still too young to be worth the trouble. So the one new thing Rust does bring to the table isn't really ready yet.

D's new things have been more accidental than by design... and kinda subtle too. Like the compile time reflection. I'm sure someone else has done it somewhere before, but D makes it really easy.

Re: D 2.069.0 released, compiler automatically ported from C++ to D

#107

Earlier quoted context omitted.

null deference in D doesn't throw exceptions by default on Unix so you won't see the backtrace there. If you are working in a big codebase and have this come up, you can enable core dumps and run it in a debugger to get far more information than just a line number (and line numbers are there too at least if compiled in debug mode).

does this mean there is not a way to get stack trace on OSX?

I don't know about an automatic one, but running the debugger would still work there too. Or at least it should.

Re: D 2.069.0 released, compiler automatically ported from C++ to D

#108
post #101

Earlier quoted context omitted.

> higher-kinded types Well, not really. Higher-kinded type parameters are something that requires a kind (typeclass) system in the first place, which D intentionally doesn't have (as D's authors are opposed in principle).

kinds and typeclasses are rather different, are they not?

Yeah, I shouldn't have made it read like I was equating the two. What HKT means is that typeclasses, like Monad, can take parameters of higher kinds. But if you don't have typeclasses in the first place (like D doesn't), then you don't have HKT.

Re: D 2.069.0 released, compiler automatically ported from C++ to D

#109
post #66

Earlier quoted context omitted.

As someone who's been following the hype, but not really jumped on yet, the difference (whether real or imagined) seems to be that rust is trying to do something new , and D looks to be (and I've seen it aggressively marketed as) C++ with some better choices and cool features. Personally, I'm not really interested in C++, but I am interested in getting for familiar with a systems language, so rust interests me.

From what I understand, the only new thing Rust is contributing is managed lifetimes. Everything else is, like in D, just borrowed from other languages and put together. That said, I've mostly heard that lifetimes are still too young to be worth the trouble. So the one new thing Rust does bring to the table isn't really ready yet.

> That said, I've mostly heard that lifetimes are still too young to be worth the trouble. So the one new thing Rust does bring to the table isn't really ready yet.

Not in my experience. I wrote tons of safe Rust every day and I really enjoy not having to worry about difficult-to-debug crashes, undefined behavior, and security problems.

Re: D 2.069.0 released, compiler automatically ported from C++ to D

#110
post #93

Earlier quoted context omitted.

Since 1.0 last May, we have a strong commitment to backwards compatibility as well. Stability should not be an issue any longer.

My impression is that things are settling down now, but I've encountered quite a few rust code bases that required "latest rust" (latest > 1.0) - and even "nightly". Not to say that rust-the-language hasn't stabilized, but I think the point about D being (way) more mature still stands? (Note, it's a good thing that people are writing code to test/work with/exercise latest rust/nightly etc -- but just because I can be…

> quite a few rust code bases that required "latest rust" (latest > 1.0) - and even "nightly".

In my experience most of these either use old features which have a stable counterpart, or use compile-time codegen (there are stable libraries to do this now, though they aren't as ergonomic as plugging into the compiler directly)

Post reply on HN