It's especially misleading because "services" like Amazon RDS and the provisioning systems offered by the big IAAS providers are listed and the self-hosted (+- open source) alternatives don't get mentioned.

One could write a whole essay on the inability of this $4bn company to fix the most basic bugs in their product. I'd love to see evidence of people actually usefully using the features like this that Splunk provides.

I work in the BI / analytics space, with a fair amount of what's called "big data". The security of something like cloud IO is typically not too much of a concern on the kind of projects I work on: more often than not, our clients deploy dedicated analytics databases. Perhaps I'm biased as we tend to work from the outside, but I'd be surprised to find many sysadmins allowing chart IO to connect to the production DB. The ETL process for analytics databases tends to either obscure user data or aggregate it to an impersonal level of detail.

I'm more concerned about the more enterprise-y products aggressively advertising 'enterprise' security features like Active Directory integration, smoothing over their total lack of transparency in vulnerabilities and bugs.

And yet reddit is corporate-owned, being hailed ITT as "the mainstream media", and there's plenty of evidence of senior Reddit moderators showing solidarity for the more criminal subreddits. Defending Reddit's dark side by comparing it to the wild world of message boards and comment sections is disingenuous: Reddit has a pervasive culture of "free speech" at all costs, and this is a consequence of it

>showing solidarity for the more criminal subreddits.

Like?

/r/picsofdeadkids /r/beatingwomen

I know the original remark was "more criminal", but are these criminal or tasteless and ugly?

Indeed. Nice little sleight of hand where the article reference "mainstream media" and then switches to "mainstream blog media" before citing any examples.

Can you recommend any resources for writing performant code for canvas / SVG?

> I like people in Wisconsin, can't really relate to people in Chengdu,

?? They're just people.

Sure, but let's make no mistake: the people in Chengdu don't buy into this silly idea that they should care as much about the people in Wisconsin as they do about their neighbors just because "everyone is just people."

And yet I've met people from Xinjiang and Sichuan who share my feelings about other people and view things through the lens of international solidarity on a personal, human level. What's your point? That the risk of 'white guilt' is a reason not to discard indefensible perspectives like xenophobia and othering?

I have no control over what people in Chengdu think about me. I can only control what I think. I think I'm stronger as a result of free trade, and I even think that's true for my family, community, state, and nation.

Sure, but they probably feel more a connection to people locally. This is reflected by the psychological concept of propinquity. It's a powerful influence in our world.

People in Wisconsin are people I might meet. People in Chengdu are people I will never meet.

> Essentially, the financial aid programme is the PyCon Outreach program - it's the community holding up the community and making itself accessible at this major event through these financial grants. It is the very spirit of the conference; make the information, knowledge, friendships and connection available to everyone.

Love this. Too often, conferences & groups that are all about 'openness' and freedom don't make allowances like this to actually expand the reach and the appeal. Linux Australia do a good job of this.

Yep, futures can be done easily in Go with a goroutine that sends a single value on a channel, but: 1) you can't dereference the value multiple times in Go, so you have to manage saving it yourself, and 2) there's no syntactic sugar. Pity.

You could save the future in the Future implementation

    type future struct {
        completed   bool
        result      interface{}
        ch        <-chan interface{}
    }

Edit: Or just check if the channel is closed

    func (f *future) Wait() interface{} {
        v, ok := <- ch
        if ok { f.result = v; return v }
        else  { return f.result }
    }

The Arch package maintainers' job mostly boils down to managing the PKGBUILD. If you get comfortable using ABS your experience with Arch will improve dramatically.