Linked by Thom Holwerda on Mon 11th Feb 2013 22:59 UTC
General Development "I feel like writing about the Go programming language (or 'Golang') today, so instead today's topic is computer stuff. For the record, the language I've programmed the most in has been Python, so that’s the perspective I'm analyzing it from." Some good and bad things about Go.
Permalink for comment 552200
To read all comments associated with this story, please click here.
RE[2]: Meh
by moondevil on Tue 12th Feb 2013 08:40 UTC in reply to "RE: Meh"
Member since:

I took a look at Rust awhile ago... but it just didn't look like a fun language to use. So I'm curious about why you find it more suitable than Go.

- Macros
- Proper type inference a la ML
- generics
- non nullable types
- sum types
- exceptions

The only thing I don't like in Rust is the Perl syntax influence in how pointers get declared.

D is one of those languages that I keep meaning to poke at, but never get around to (because there's really nothing there except nicer syntax.)

It is really a better C++, not only syntax.

You get to do meta-programming with proper language support, not the C++ template hacks.

Safer than C++, because you are require to state which code is unsafe. In C++ even if you restrict yourself to the safe language constructs, you need a static analyzer to proof it.

Whereas D is safe by default unless you make use of system modules/sections.

Go strides exited already in D before Go was created.

Additionally both languages have:

- some form of automatic memory management
- modules
- support for concurrency
- follow the school of thought where the developers have the same facilities as the compiler writers to create data structures.

Reply Parent Score: 3