Blood wrote:
I tried go but the lack of parenthesis put me off the syntax.
You can add parenthesis in IFs and FORs if you want to.
(if this is what you are talking about...)
Actually you can add them every where you want...
Blood wrote:
I prefer the D language instead.
I just went the other way around.
Started looking into D years back and wrote ~50K of useful code and now I get somewhat annoyed:
After all these years:
GDC is unusable on Windows - DMD compiles my program just fine but GDC does not (newest version)
There will be no DMD for 64 bit Windows. So on 64 bit Windows GDC it is.
The language seems to shift and loose the easy syntax that D v1 had.
Sure they tried to fix things, but every time I look at some D v2 code it get's more complicated and weird.
(especially with complicated code, duh...)
Maybe the major problem of D is that it tries to be all things to all people - and with that it satisfies no one completely.
(except the people involved in the compiler/language)
Go seems to go the other way and tries to simplify the needed syntax - especially for complicated code.
The compile time is very, very fast compared to C++ or GDC (DMD is acceptable but still way slower than Go) .
It is already used inside Google on different projects which tells you something about the state of the compiler.
Compiling is easy just do:
Code:
go build hello.go
And it creates a hello.exe
The smallest possible hello world program is ~200kb (64 bit) if the internal printf is used.
With fmt.Printf the size grows to ~1.2mb (64 bit) because of the runtime.
But even with D a program with ~50K of code compiles with DMD now to ~500kb (32 bit) and it used to be ~1mb a few versions back (depending on the library functions used)
Last weekend I bought a e-book as PDF (The Way To Go - 629 pages -$3.99) about Go and started reading it whenever I can.
BTW: Go is BSD licensed and the "Google" name is not in the code - they left it out.
Also (as with D) more and more people from the outside are involved in it.
Maybe when I'm done with the book I will find out that Go doesn't suit me, but for now I'm pleased.
Ask me again when I wrote ~50K of useful code in Go
