Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Go is 3 years old. Also, golang addresses more than just this issue, the concurrency approach is interesting for example.


D is 11 years old and solves the exact same problems plus it uses a more traditional approach to objects.

The big difference is Go has Google+Pike pushing it and might actually get widely adopted. Getting some improvement is not a bad thing.


The big difference is Go has Google+Pike pushing it and might actually get widely adopted.

I don't think it is just that. There is also a difference in culture and tradition. Roughly, Go fits more in the C and Python tradition, D and Rust fit more in the C++ and Haskell tradition. Simplicity versus formal correctness.

I think the Python/C pond is just larger than the C++/Haskell pond.


Considering one of the goals of the language is simplicity, I don't see how D has solved this problem.


Because everyone else doesn't want to throw away the last 20 years of language design.

Go's search for simplicity is seen as a solution looking for a problem in the language design communities.


Go's search for simplicity is seen as a solution looking for a problem in the language design communities.

But most programmers are not in language design communities. There is a big potential for a 'safer C' or a 'faster Python'. Yes, that's a simplification, but also how people will see Go.


> 'faster Python'

Why throw away Python's capabilities to execute it faster? Just make use of PyPy.


PyPy is geometrically about halfway between CPython and Go, performance-wise.


For the type of applications Google is showing off with Go, I doubt it matters.


I do not mean this as an attack but have you written much actual "real" Go code?

There are several reasons I'm interested in D and more so Rust, but they're very different than Go.


I do not mean this as an attack but have you written much actual "read" D code?

See how this never ends?


Not really given that I think you're missing out on the advantages of Go, looking for the wrong things and generally missing the point of the article entirely.

And yes, I have. Hence my comment.

Er, you weren't the GP, sorry, but my point remains, though somewhat directed a cjensen.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: