The American citizenry tends to be OK with this kind of thing as long as it happens far away from us. But imagine the reaction if the cafe where this occurred were in the US, and the drone was controlled by a foreign government. That singular event would ignite a US invasion or possibly nuclear assault against the country responsible.

People in other countries are also people. They have the same reactions and emotions that we would when a foreign entity blows up their businesses, families, and friends. We have so far been lucky that none of our victims have had the military power and political will to retaliate in the vicious and violent manner that we would. That will not always be the case, and I do not look forward to the day when our own brutality is visited upon us.

This disgusts me.

Sooner or later, my public announcement of this disgust is going to place me on a list of people that are seen as dissenters, since all of our electronic communication is now being logged for posterity. That list will at some point be renamed "terrorists".

At some point in the future (as a non-American), the United States would find it legally acceptable that I can be targeted by a drone and blown up into little pieces. Should wife, my children (one a toddler and the other a baby) happen to be present, then they will be considered "collateral damage".

I love the idea of the American dream and the spirit of free speech and the glorious constitution that you have / had in America, but I'm sorry, you've just lost me. I'm like a lover you just beat up for the first time. I've lost that sparkle of first love. I'm crying inside. I'm scared to show you that emotion, because I'm afraid you'll use it against me.

You're a bully and there is no teacher to get you back in line. You scare me.

I know this will get downvoted to hell, but I just had to splurge my mind.

Is there any more impressive open source project than Wine? I mean, yes, the Linux kernel itself and maybe GCC, but Wine just blows me away. The sheer audacity of sitting down and deciding to reimplement the entire Win32 stack including bugs to the point where DirectX is reimplemented in OpenGL and everything runs natively is just unbelievable. It's truly a testament to open source. No business would initially fund a project like this, it's nuts. And yet it exists, and continues to improve, and now companies like Codeweavers are built upon it. Congrats!

Go developer here. I posted this on the blog too.

""" This is a mistake, plain and simple. It was pointed out on the Go developer mailing list a few days before your post, and you can see my reply there.

NewRequest should take an io.ReadCloser. Unfortunately, due to backwards compatibility, a long standing semantic mistake like this is not something we can just fix, but we've at least documented it.

The tweet you quoted is wrong, and I want to explain why. If an interface value v is passed to a function f, then what does happen from time to time is that f will look for custom methods on v that are at least logically equivalent to the static interface type f is declared to expect. For example, io.Copy takes an io.Reader and an io.Writer and does the obvious thing, Reading into a buffer and then passing that buffer to Write. Of course, it would be nice to bypass the buffer when possible, and so there is a standard WriterTo interface that an io.Reader can also implement that, in contrast to Read, which copies into a buffer, says "read the data out of yourself and directly into this Writer". If io.Copy finds that method, it will use it, but the operation - reading - is the same. There is an analogous case for the Writer too. If you pass a value v to json.Marshal, Marshal will check to see if v implements json.Marshaler, meaning v knows how to marshal itself as JSON, in which case v is given that opportunity. Again, same operation you requested.

In contrast, if you have an io.Reader, while it might be okay to look for other Read-like methods, it is certainly not okay to look for Close. That's a very different operation, it's surprising, and it shouldn't be there. FWIW, I'm not aware of any other instances of this kind of semantic mixup in the standard library. But again, unfortunately, we can't change it until Go 2. All we can do for now is document it and move on. """