luriel

When your whole business model is based on government granted and government enforced monopolies, you have very little right to complain IMHO.

Most medical research already happens in publicly-funded bodies, bit it is then spun-off and captured by big pharma.

Not to mention that as many have pointed out over and over again, the main expenses of drug companies are not research, but drug approval bureaucracy and marketing.

It is a textbook case of regulatory capture.

Still, abolishing patents would go a long way to allowing real competition and progress in healthcare.

Actually this a well known process known as regulatory capture.

Where the regulated industry ends up in some kind of symbiosis with its regulator, encouraging it to both grow and to keep competition at bay.

The conflict between the regulators and the regulated industry is largely a farce as they know they need each other.

This is a good move, any government using Oracle is wasting taxpayers money and being irresponsible and negligent with its citizen's data.

One could talk of NSA backdoors, but there is no need, the security of Oracle products is laughable at best, there is no need for backdoors.

If you hire a Go programmer, it probably will be somebody that deeply cares about their work, somebody who has a certain sense for aesthetic and technical simplicity, and other qualities that not common that among Java programmers.

I count this as a Go feature.

you can also add just after import "fmt" add: var _ = fmt.Println

That way it will never complain that fmt is imported but not used.

Still, I never had need for this. Once you have written a bit of code the import list remains relatively stable.

Go does incremental compilation just fine.

Nobody has bothered to add parallel compilation because building Go code is already so ridiculously fast.

Full case folding is already in tip and will almost certainly be part of Go 1.1.

> This seems like needless boilerplate: why not instead simply pass a closure over a channel that the goroutine will execute? I have never seen this technique used in Go, but it seems natural to me. (It's essentially how libdispatch works.)

Passing a closure on a channel is both idiomatic and relatively common in Go code.

This and other comments make me suspect the author could have benefited from spending more time looking at existing Go codebases (the source of the Go stdlib is excellent).

Edit: His (IMHO somewhat strange) complaint that "Channel reads violate the laws of time and space by changing their behavior based on how their return values get used." doesn't apply anymore, now to do async reads from a channel you use select with a default, not the comma-ok idiom.

Also a package including more 'clever' Unicode operations will also be part of Go 1.1, but I have personally never found the existing support lacking, and no, I don't live in an English speaking country.