/prog/s opinion on Go

You know, the google thing.  Personally I'm a bit excited for a compiled python-like C language.  It's going to take for fucking ever for it to become useful, though, especially with google's slow and steady attitude.  I could see it catching on though kind of like python did.

>>51
How about allocating an array and then adjusting the pointer afterward, so that accesses to a[-1] or a[-2] are valid?
Or any case where you're iterating something and passing it between one function and another; if you can't manipulate pointers, then you have to pass around two variables for the array and the current index, and your functions have to account for this instead of simply writing a[0] a[1] a[2] etc. and adjusting the pointer when calling it.

Both cases can be "fixed" by adding more syntax to the language, but it's entirely unnecessary because a perfectly decent way to handle these scenarios already exists.

I have a feeling that in some years, people will rediscover low-level languages and pointer manipulation in much the same way that Lisp is currently being rediscovered.