Go, Google's New Open Source Programming Language
Many readers are sending in the news about Go, the new programming language Google has released as open source under a BSD license. The official Go site characterizes the language as simple, fast, safe, concurrent, and fun. A video illustrates just how fast compilation is: the entire language, 120K lines, compiles in under 10 sec. on a laptop. Ars Technica's writeup lays the stress on how C-like Go is in its roots, though it has plenty of modern ideas mixed in:
"For example, there is a shorthand syntax for variable assignment that supports simple type inference. It also has anonymous function syntax that lets you use real closures. There are some Python-like features too, including array slices and a map type with constructor syntax that looks like Python's dictionary concept. ... One of the distinguishing characteristics of Go is its unusual type system. It eschews some typical object-oriented programming concepts such as inheritance. You can define struct types and then create methods for operating on them. You can also define interfaces, much like you can in Java. In Go, however, you don't manually specify which interface a class implements. ... Parallelism is emphasized in Go's design. The language introduces the concept of 'goroutines' which are executed concurrently. ... The language provides a 'channel' mechanism that can be used to safely pass data in and out of goroutines."
You're a bitch and i'm gonna rape you like one. Bend over fag.
Failed to read the parent. Parent's complaint is that you have to start loading a bunch of modules to do anything. The reason everything that I write is in bash, perl or visual basic is because I don't start with "uhh, okay, #include , #include ... etc.
Nope, I'm not a dickhead, I mean a programmer. I used to employ a few, but they were generally dickheads, so I outsourced them. The brilliant ones (not a single one with a CS or CE degree) I kept, but not as programmers.
yeah because it won't scale up you fucking twit. I think you're another one that needs a cock in your mouth and especially in your ass. I'm gonna bring the niggers with me over to your house and show you what 581K is nothing compared to what you're gonna get.
""Open Source" for the geeks, "Google Branded" for the techies, and "Apple" for the wanna bees?"
I hear that. I've always enjoyed a good chuckle when limp wristed graphics artsy and English pedants make a comment implying mac users tend to be more tech savvy.
The mac is a platform that thrives on being intuitive and idiot proof. A system where you need know nothing about hardware or the nuts and bolts of the system. Even power user keyboard shortcuts are an afterthought. At the beginning of the millennium MacOS still lacked viable multi-tasking and required third party software to enable virtual memory.
And yet people who know nothing of the hardware or the software, don't realize they should demand multi-tasking and virtual memory, who apparently didn't rely upon power user features like keyboard shortcuts and command lines. They were the supposed tech savvy crowd.
Good find. OMFG, only a retard uses tabs. JC. Insanity.
> PHP? Where they dump all their million built-in functions into one namespace? Lame.
And let's not forget the utterly dreadful naming standards used. So you get crappy "DOS" style abbreviated function names like "str_replace", "str_split" and "strcmp" instead of something meaningful like "StringReplace", "StringSplit" and "StringCompare".
It's high time that programmers stop using crappy abbreviations for names in programming. We're not dealing with DOS systems with 8.3 filename limitations and there's no call for laziness. Using a modern IDE you only have to type the bloody name once anyway (when you declare it) after which the IDE will autocomplete for you.
You don't need an IDE, just a decent editor that can do autocompletion. These sorts of editors have been widespread since the 1980s.
A better reason for shorter names, and one I still heard seriously argued less than a decade ago, was the relatively narrow, 80 character screen width. Long names can eat this up fast, especially if your function bodies contain nested, indented blocks.
However, we now live in an era where 80 character screens are unlikely to be a limit to working programmers, though, as I said, I've heard it argued that sticking to this 80 column limit allows multiple, side by side program text windows on a single monitor, and so should continue to be standard.
"Ken Thompson, who invented Unix..."
Yes... about that.... the problem is, Unix isn't exactly the best designed OS of all time. It's there, and it runs, but it's not necessarily pretty.
It survived, like C, so that says something... but mostly about how abysmally awful all the other alternatives have been.
Go looks like a small step forward, in some ways, but... sigh. Better, but so little better.
You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC