They weren't overhyped. Your point is a common and old canard.
The worry wasn't that avian flu or the swine flu would kill a lot of people in their current states, but that they would mutate into something considerably more dangerous. The swine flu, for example, was known to spread easily but wasn't _yet_ very lethal. The avian flu (H5N1) didn't _yet_ spread easily, but was very lethal.
If the swine flu mutated into something more lethal or if the avian flu mutated into something more communicable, then everyone would probably know someone that died from either virus. And that's exactly the worry with these new crop of viruses, and why it's important to react with extraordinarily measures -- to prevent them from becoming something much worse.
The Java frameworks are generally doing very well (top quarter to top half), and the PHP frameworks are generally doing very poorly (bottom half). PHP-raw is doing well, but that's not heartening given how mature its frameworks should be (if we were talking about golang, I think that argument would be sound).
I was considering other factors in that generalization, although they're implicit. E.g., a lot of the "cool" language frameworks I mentioned are comparable with the Java frameworks in speed, but Java has a considerably larger ecosystem and number of hirable developers (although I'm not sure if that translates well into web development). And I assume PHP is as verbose as Java from what I've heard from other people (I've never used PHP).
What language should be the conservative choice based on the many factors and ignoring the specific case for the general case?
Java should be the conservative choice for your web framework's language (rather than PHP). Scala, Clojure, Nodejs, Erlang, Lua, and Haskell should be in your list of workable yet "cool" languages (rather than Ruby or Python).
Yes, you can do all of those things with sublime's API (https://github.com/wuub/SublimeREPL, https://github.com/SublimeText/Origami). Yes, emacs is more extensible, but not where it matters, really. I.e., I don't think you're going to see any cool feature made with elisp that can't be ported to sublime.
I'm guessing, but I think it's because yesod uses a lot of magic such as templates and the like. The other frameworks like Snap use more idiomatic Haskell.
I think Adria could have avoided this if she apologized not for reporting the offenders to pycon, but for publicly identifying them. She was given the perfect opportunity for this when one of the offenders apologized for their own misstep in a hacker news thread that she herself commented in (https://news.ycombinator.com/item?id=5398681).
You have it backwards. I don't care how racism is defined. I care about whatever the word "racism" points to in the real world. But you have to realize that a word can point to anything you want it to point to.
And not only that, but words have denotations and connotations. "Ugly", in common usage, denotes and points to a set of subjective physical characteristics. "Ugly" also connotes and points to a negative affect that isn't explicit in its denotation.
I'm not simply saying that racism is "something that connotes immorality", but that is what we're connotating when we use that word in its various denotations (although, it's not necessarily the case). Racism's denotation can be literally anything. I can say, for example, that it's racist to call Canadians effusive pushovers even though "Canadian" is a nationality rather than a race.
And people do exactly that. In the U.K., for example, it's common for people to call people that insult the French "racist."
Language is fluid.
So, I think you can see why people are affronted when someone says "black people cannot be racist" without putting it within a certain context. The implication is that it's not immoral for black people to act denotatively common-usage-racist.
You're lacking an understanding of linguistics and philosophy. Both usages are no more correct than the other, and the point of such usages is to ascribe a connotation to a cluster of things along a continuum. Arguing over definitions is pointless (I can create my own definition of racism and it will be equally valid), the point is what they connote.
That's all a bit silly. We have a common understanding or definition of what racism is and it connotes something immoral. _Some_ sociologists define racism as something else which also connotes something immoral. The common thread is that both definitions connote immorality, and so if something falls under either definition, it's still bad and so the whole arguing over which definition to use is moot.
For example, if an organized group of American Asians began touting their superiority over other races and advocated and lobbied for more Asians in positions of power because they're superior, wouldn't you still consider their actions to be immoral?
People can use whichever definition they like, but they need to be open about it, and they need to realize by using another definition they're not also redefining or constraining the connotation -- that's begging the question.
So, black people cannot be sociologically-racist-therefore-immoral against white people, but they can be common-usage-racist-therefore-immoral against white people.
(I should also note that labeling something with a word that connotes a negative or positive affect isn't much of an argument for the applicability of that connotation to that something. It's a heuristic more than it is an argument.)
Personally, and I think this might be the case with most people here, I'm most worried by the public shaming of the two individuals. Them being kicked out of PyCon isn't as much a concern to me.
I think the culture that she's implicitly promoting is ultimately a suspicious and hostile one where there is no principle of charity but instead there's the inverse (http://en.wikipedia.org/wiki/Principle_of_charity). And not by the fact that she reported it to PyCon organizers, but by the fact that she then escalated it to the public. In this instance, I think she should have kept their identities anonymous in her tweets and blog post.
There are instances where I can imagine revealing their identities would be the right thing to do, but this doesn't come close to it by my judgement (for all that's worth).
I'm clear on that. This whole issue is deeply entwined with philosophy which makes it all a bit amorphous. From one perspective, you could argue that it's moral to boycott SendGrid if it leads to "positive" consequences, for example.
"I'm pretty sure relating and disclosing a situation that happened in a public place fully to the best of her ability shouldn't be something we call irresponsible. In fact, women who do otherwise are often asked to disclose in exactly the manner she did."
That doesn't follow -- you're begging the question. Why is disclosing something public, if well detailed, not irresponsible when it can cause harm (as this situation did)? And why should people being previously asked to disclose such information make it a responsible action? Furthermore, do you have an example of such disclosures -- you speak as though you do?
I got the impression reading Adria's blog post that she thought she was responding to sexism. Sexism is what most everyone is responding to in this event -- real or imagined.
The problem is that the way Adria responded, in part, harmed people that didn't deserve harm (and if they did deserve it, it shouldn't be up to her to mete it out -- which by taking it public she is effectively doing). She should have kept their identities anonymous unless it was necessary to do otherwise.
In a culture that strives to be politically correct (no negative connotation intended), any egalitarian issue can be wielded like a weapon. I think Adria was aware of that, and so I think she deserves a fair amount of blame for the events that followed her actions.
The worry wasn't that avian flu or the swine flu would kill a lot of people in their current states, but that they would mutate into something considerably more dangerous. The swine flu, for example, was known to spread easily but wasn't _yet_ very lethal. The avian flu (H5N1) didn't _yet_ spread easily, but was very lethal.
If the swine flu mutated into something more lethal or if the avian flu mutated into something more communicable, then everyone would probably know someone that died from either virus. And that's exactly the worry with these new crop of viruses, and why it's important to react with extraordinarily measures -- to prevent them from becoming something much worse.