uriel

> The old standard file permission system is the default on most unixy systems because it's easy to use and understand

And that is exactly what makes it more secure than ACLs which are extremely complex and unwieldy to setup and manage.

Except that the "idiomatic" implementations were not idiomatic, and the "optimized" versions were not optimized either. The whole paper was a huge joke.

> Russ Cox (also a Googler) "shreded" the paper here without himself passing it by the Scala enthusiasts for their take on it, etc.

But russ didn't claim anything regarding Scala, the problem with the original paper is that it made explicit and implicit claims regarding Go, Scala, Java, etc. without really bothering to make much of an effort to make the comparison minimally realistic.

You are not alone, I'm also very reticent to adding yet one more complex tool into my systems when a few simple and clean shell scripts can do the job.

Most Go code I have seen was non-academic and practical. See for example doozer: https://github.com/ha/doozerd and camilstore: http://camlistore.org/

You can look at the memory usage here: http://shootout.alioth.debian.org/u64/benchmark.php?test=all...

I used XFS for years, until I got tired of it semi-randomly overriding my files with zeros and then found out that apparently this was 'by design', after that I stick with ext3/4 that might not be as fast in some corner cases, but which are just as fast or more with my usage patterns, and which so far has been good at not corrupting any of my data.

If you are using the 32bit compilers, there were issues with the garbage collector for a while, in any case you should always use the 6g 64bit compilers for any serious work, they are much better tested and generate more efficient output.

Other than the issue with the 32bit compilers, I don't remember hearing of any leaks in Go.

Erlang has a slightly different but largely equivalent model, but the other alternatives you mention lack Go's channels and/or the select construct which is one of the greatest things about the language.

When I found that Stackless Python didn't have a way to read/write on multiple channels at once I was quite shocked.

Given that the guy that wrote this article was clearly not very versed in Go and made some pretty basic mistakes, I'm not sure how you can say he is part of whatever "Go folks" conspiracy you are claiming.

> I've got a PHP project at http://fstr.net and its pageloads take about 4 to 5 seconds under normal load.

Whatever language you are using, if loading a page takes >1 second, you are doing something very wrong.

I have built web apps out of shell scripts that perform hundreds of forks and open dozens of files per request, and still easily managed <200ms response times while running on a crappy xen server.

Many people consider Java to be C++--

The Go x64 compiler (6g) has gotten more attention than the x86 one (8g), and I think given that this days most systems are x64, this benchmarks page is more representative:

http://shootout.alioth.debian.org/u64/benchmark.php?test=all...

Go is C-like, D is C++-like.

The Go distribution already contains plenty of idiomatic, well written and very readable code.

Free speech means being free to say things others might not like being said.

If free speech only covers things that others might find acceptable, then it is completely meaningless.

Hopefully they will be rewriting in Go ;)

Interestingly many rubyists seem to be joining the Go community lately.

Java is the new COBOL. In practical terms, there is little real difference.

Java is way more complex than it should be, specially after badly botched features like generics were added.

> There are many stable oligopolies which can either resist, tamp down on, or co-opt new upstarts and maintain a status quo for themselves.

Can you please point out some of this many oligopolies that somehow force me to do business with them? I can not buy from pretty much anyone I don't like, if I avoid paying taxes I will probably end up in jail.

Of all the VMs you mention, the JVM is by far the least portable of all.

Actually, Go would be great for GUI programming, precisely because it has a concurrency model that doesn't suck, and GUIs are almost always concurrent. Remember that Go's concurrency model is a descendant of CSP which Rob Pike first used in Squeak, a language designed exclusively for building GUIs: http://doc.cat-v.org/bell_labs/squeak/

The JVM is "cross platform" if you only care about no more than three platforms.

If you want to run it on anything else, you are pretty much SOL.

This is not what anyone should call portable.

> where Rubyists and Pythonistas are monkey-patching metaclass decorators

I hate Java, and this is one of the main reasons I also hate Ruby and Python.

The opposite of the Java-bureaucracy is not necessarily "features" that are a few times over too clever for their own good.

If there is only one thing Java ever got right for example is to avoid multiple-inheritance and operator overloading.

Also the Java vs. C++ dichotomy you present is not shared by many Java hatters, just take a look at all the quotes here that mention C++: http://harmful.cat-v.org/software/java

This is one of the reasons I love Go, it is preeminently pragmatic language, not designed for "mediocre programmers" (Java) or "genius programmers" (Ocaml, Haskell, C++), or to fulfill feature checklists, but to be useful and used by hackers that want to get stuff done and not just to think about stuff.

This is a good time to remember John Perry Barlow's "A Declaration of the Independence of Cyberspace":

http://doc.cat-v.org/political_science/cyberspace-declaratio...

Sorry for the snide comment, but if you want to really speed up your Rails, switch to Go, it will compile from scratch and start up your project faster than the ruby interpreter starts up.

I used rails in a few projects, and performance was so painful even on pretty good hardware that I said never again. Go on the other hand is pure pleasure.

One of the reasons I'm starting to love Go more than Python.

In Go something like super() is superfluous.

They are good for creating jobs and selling expensive enterprisey software packages to PHBs.

There is a "Custom Search Engine" for Go: http://go-lang.cat-v.org/go-search