Have you programmed in Google's GO programming language by Google today?
Their Hello World is weeaboo!! It must be good!
Name:
Anonymous2009-11-11 0:39
Go has fast builds, clean syntax, garbage collection, methods for any type, and run-time reflection
Sure doesn't seem like a systems language to me - honestly, it seems like a replacement to the shit-show that is Java. It couldn't have gotten here soon enough. Not sure why they're calling it a systems language actually.
Some of it seems extremely attractive, in particular slices; that looks like a truly great language feature. Built-in concurrency looks really good; no other language has done this properly, and most new ones don't even try (I'm looking at you, Python). Another thing that in my opinion is good:
Go does not support function overloading and does not support user defined operators.
It's like D done right. It's like managed C with built in GC/threading libs and all the old legacy and error prone shit cleaned out (built-in arrays, no header files, no automatic type conversions, case labels don't fall through automatically, etc).
Some really nice improvements over C++; for instance C-style method declarations only (no duplicate syntax), open classes!!!, new() is a function, automatic interfaces (static duck typing! roxors!).
Here's one thing that doesn't look good:
When a package defines an object (type, constant, variable, function) with a name starting with an upper case letter, that object is visible to any other file which imports that package.
Having the language interpret naming conventions for things is a bad idea. It was a shitty idea in Python and it's still a shitty idea.