Well, since you're unwilling to think, I'm not going to do it for you.

I was just posting to see what the general consensus was to be honest .

Personally, I think that it sounds like a good idea in that Python and C++ are both powerful languages and the combination could balance out each language's disadvantages but I'm not entirely sure how that would work smoothly.. and even though the idea sounds nice I'm not so sure I like it running under Google - 'evil' is a strong word but..

I guess it depends what their plans are for it.. and maybe how open they are about developing it further.

Well, I like it. In particular, slices, rather than pointer arithmetic, is simply The Right Thing.

I have been looking for a good safe systems programming language, and it seems like garbage collection is the practical thing to do. The other option is Cyclone, which I don't like.

Looks like google doesn't let this language run on windows because windows is too popular. hehehe At least it will run on linux and mac. Unfortunate that it's not cross platform for all systems.

>Looks like google doesn't let this language run on windows

Oh, well that sucks. Not a fan of languages that aren't easily portable.

not even if it's mixed with such excellent features as Python's.

Sorry I'm not able to burst into enthusiasm. The statement alone, they would combine Python's development speed with the "safety of a compiled language like C or C++" is a farce. C++ is one of the unsafest languages out there. Not to mention the ugly syntax

One really cool hybrid between dynamically and statically typed language with a great syntax is Boo. Another language that already provides most features of Go's is D.

I guess Google's move has market-strategic reasons more than everything else. Nonetheless I would very much welcome a truly safe (unlike C++) system programming language that is backed by a strong player in the market and does not suffer from the resource hunger of .NET and Java.

It seems Go will be used so much on server applications that's why windows has not been considered.

Maybe Windows is simply too unsafe for Go.

Actually the syntax looks a lot like a mix of Object Pascal and C++, not sure where the beauty of Python went.

I think that quote is referring to type safety. Not to mention monkey-patch safety. If you know how to use C++, it's a very safe language. C++ provides the best "resource safety" of any mainstream language.

Go is a variant of C and has a type system very similar to C's. I think it's a great place to start -- it doesn't have exceptions, so the behavior of things is very predictable. I can imagine projects where I'd normally use C, but now I'd use Go. And Go has room to grow.