For one, that Facebook post read pretty much as described above. Comparing someone who complains about vicious, nasty humor like "rape-me" and "recursive_pimp_slap" in a highly public place to "women who want to make it all about their vagina" and saying that people are "co-opting male spaces" pretty much says exactly that. It says "yes, it's hostile to women, and any women who complain can be reduced to a single anatomical feature, and if you complain you're trying to co-opt my playspace." There's really not much wiggle room in interpreting it.
a certain faction of extremists
The problem is that many people who are making reasonable points, like someone who's pointing out that gems named "rape-me" really aren't acceptable in polite society, wind up being lumped in with extremists.
There may be a few extremists out there, but not many. What you see lots more are people who are tone deaf and make problems worse by going around and yelling "you're racist/sexist/homophobic", "no, you're a feminazi/PC", and on and on without ever really getting anywhere. Most of those people (on either side) aren't extremists, they're just caught in the internet spiral of hate. But just because some people go overboard on the internet spiral of hate that simply amplifies problems, doesn't mean that there aren't some real problems.
So, responding to someone who says "rape-me is not an acceptable name for a gem" with such rhetoric is instantly escalating that internet spiral of hate for no reason. Lumping people who have legitimate complaints, like "let's not have rape references in our public software repositories" or "let's try not to sexually assault people at conferences" with "extremists" is a way of dismissing those legitimate concerns and simultaneously escalating the rhetoric to the point where nothing useful will come of it.
whinging about a Torvalds rant on the kernel lists,
or the extended brouhaha from the "donglegate" thing
from earlier in the year
These are two very different issues. One is a question of whether it's a good idea to chastise your collaborators so strongly on a public list, or whether there could be more polite ways to make your opinions known. It didn't really have any kind of discriminatory or sexist content, simply a question of the best way to encourage good practices and discourage bad ones.
The other is somewhat more relevant. It's an example of puerile humor, in a private conversation that happened to be in a public place (at least, as far as I've been able to gather). I found that it seemed to be an excessive attempt to shame people for behavior that was, as far as I can tell, supposed to be private, but was in a public place so other people could overhear it. I think that there is some reasonable debate to be had over what kind of behavior is appropriate in a public space where you can be overheard, but that there was an overreaction to it, since it was private behavior. However, the internet spiral of hate wound up blowing the whole thing out of control, in part because there are so many people who are so sensitive on both sides of these issues, and it went way beyond anything it should have.
Here's the thing. Donglegate could have been someone pointing out behavior that she considered inappropriate, and people could have taken that to heart and moved on. But lots of people overreacted. Posting people's pictures online publicly, rather than either talking to them yourself or letting PyCon staff talk to them, was an overreaction. Firing one of the people involved in the conversation was an overreaction. Firing Adria Richards was probably an overreaction, though at that point she had shown herself to be divisive enough to not be very good at community building. Sending her death threats and calling her a slut was definitely an overreaction.
So you can see several areas here were there were massive overreactions that led to this being far larger than it should have been.
Likewise with this post, the original post was a fairly reasonable request. "Let's not have nasty, rude things like rape-me in highly public, visible, and widely used code repositories". Now, some of it may have been a slight overreaction, like mentioning "hoe" (which is a clear reference to "rake") along with these other items. But what's a good way to deal with that? Probably to discuss those specifics; say that "rape-me" and "recursive_pimp_slap" are pretty clearly inappropriate, but there's really no problem with "hoe" or "therapist", and maybe discuss his point about whether there should be an explicit filter versus applying a certain amount of judgement. Those are reasonable, appropriate ways to respond to the post, that won't lead to donglegate style escalation.
Talking about "vaginas" and "co-opting of male spaces" is, well, the opposite.
At what point is it socially acceptable to express
exasperation with a group of people who ostensibly have
noble goals, but then cause damage while they're at it?
It's generally socially acceptable to express exasperation with a group by pointing out specific flaws in their arguments, offering constructive criticism, and trying to de-escalate the situation. You should also be aware when doing so of whether you might be blind to some real problem, and that your response could come off as dismissive of that real problem; so you should try to first identify the problem that is being addressed, and understand why people consider it to be a problem.
At what point is "this is not a 'safe' space, (not in
that people are going to go out of their way to offend
you, but in that people have better things to spend their
time on than measuring their every word for the slightest
hint of '$ism'), so you may hear things that offend you,
and how you choose to interpret and deal with that is
entirely on you" ...an acceptable response?
Hmm. When people refer to a "safe space", they generally don't mean that no one is ever going to be offended by what someone else says. No one is going to measure out every word that they say, and always avoid stepping on someone's toes.
A safe space is instead one where you feel comfortable telling someone when you think they crossed the line, that they will respect that and not attack you for it.
One thing to keep in mind is that what's appropriate in one context may not be in another. Among close friends, you may feel perfectly comfortable telling racy jokes, or jokes about Jews or Catholics or blondes or what have you. When you're in the office, or at a conference, and there are people you don't know, you should consider that they may not take those jokes the same way that your friends do.
Think to yourself. If you have to tell someone "this is not a safe space", you are basically telling them "I do not want you in this space." Because if you want them in that space, you will make it safe for them. You don't have to tell your friends that, and can crack all the offensive jokes you want with them, because you know that they will be OK with it. But if there's someone there you know will not be OK with it, and you crack the joke, then you are saying to them "I would like to hurt you." Now, there are obviously nuances; sometimes you may crack the joke and only afterwards realize that it went to far, at which point you could choose to apologize and diffuse the situation (or make another making fun of yourself, depending on the circumstances).
On the public internet, recall that you can never be sure of who will see your joke, and how they'll react to your humor. Things you post to the public internet should be things that you are OK with your wife seeing, your grandparents seeing, your kids seeing, your buddy back from Iraq with PTSD seeing, a battered wife seeing, a child victim of sexual assault seeing, and so on.
If you want to do off-color jokes publicly like that, be sure to have a thick skin, because someone's sure to be offended and start trying to escalate that internet spiral of hate. This is where Penny Arcade slipped up; I think that the original Dickwolves comic was not a bad comic and not particularly offensive; in fact, it was lampooning ambivalence towards horrible things happening inspired by game design. But of course there was someone out there who got offended, and they made the mistake of taking offense at the offense and continuing to escalate the internet spiral of hate.
Sometimes, you do need to think to yourself and say "yes, I am OK with offending you." There are some people out there who try to pick apart everything and find something to get offended about in it. If you publish something publicly, you can't ever please them. But if you do, stop for a minute and decide if you really do want to offend them, of if maybe you'd rather let them be. And if you are sure that you are OK with offending them, then be sure of it, say your piece, and be done with it. Don't try to tell them why they shouldn't be offended. Don't make fun of them for getting offended. Just leave it be and move on.
(Note: same answer has to apply to pretty much any
'$minority rights' group behaving badly)
I'm curious why you call out minority rights groups. There are lots of different organizations that may have goals you agree with, and techniques you disagree with, or that you find damaging. Why do you specifically call out minority rights groups for "behaving badly"?
(This is a much better way of quoting, I think i'll do this in the future. Thanks :3)
The problem is that many people who are making reasonable points,
like someone who's pointing out that gems named "rape-me" really aren't
acceptable in polite society
That's not a "reasonable point", unless the question of "why does a program name equate to polite society?" is also being addressed at the same time. It's telling something people they already know (Hey! Did you know? These gem names are politically incorrect! This should make you upset because it will make some people feel uncomfortable!) - something which is usually not done unless there's some kind of ulterior motive.
It's politically correct, insensitive, and probably a lot of other things, I think pretty much everyone, including the guy who wrote the gem, could agree on that. Now what do you suggest we do about it, if anything?
Hemming and hawing and "How could they!"-ing not only accomplishes nothing in the great majority of cases, it turns people off of whatever valuable input you might have. Put another way, I don't think a way exists to say "This isn't PC" without coming off as a PC crusader.
There may be a few extremists out there, but not many.
What you see lots more are people who are tone deaf..
Ok wait a second here. With all due respect, that is completely and utterly your opinion and not any kind of objective fact. All I said were that loud extremists exist (something you appear to agree with me on), and implied that they are unpleasant to deal with and cause more problems than they solve.
A safe space is instead one where you feel comfortable telling someone
when you think they crossed the line, that they will respect that and
not attack you for it.
That's not how I've seen the term used, unless you expand out "respect that" you mean "police their speech and avoid offending anyone".
Think to yourself. If you have to tell someone "this is not a safe space",
you are basically telling them "I do not want you in this space."
Because if you want them in that space, you will make it safe for them.
Only if you accept the social justice definition of "safe", meaning "you absolutely will not have your feelings hurt here, and we'll smack anyone that does so.". What if the feelings of other people are not of primary (or secondary, or...) concern of your particular group? What if I do want someone in this space, but I expect them to be able to brush off some amount of non-PC dialogue because it's quite frankly not all that important to the group's goals? Is that expectation wrong? (Or worse, evil?)
On the public internet, recall that you can never be sure of who will
see your joke, and how they'll react to your humor. Things you post
to the public internet should be things that you are OK with your
wife seeing, your grandparents seeing...
Your vision of the public internet sounds incredibly dry and boring to me. Where does a place like 4chan fit into your world? What about a Carlin standup routine? South Park? I like the idea that I can go on a social network site and talk smack with friends the same way I do in real life. I like the idea that places exist where people can talk about whatever they damn well please, and if anyone else doesn't like it, they are free not to listen, regardless of their meatspace background.
Indeed, that seems like the only idea that scales.
I'm curious why you call out minority rights groups.
You misread. I wasn't "calling out" anyone, I was saying that it's socially unacceptable to call out a minority rights group for behaving badly if and when they do, because then you are seen as the enemy of whatever that group is campaigning for. The hive mind effect there is quite strong.
What he said about women trying to make a progressive movement all about their vagina? What is that even supposed to mean? How is the ruby community a "progressive movement" (yes, he was just quoting someone, but it doesn't even make sense in that context).
This was in response to a man asking that people not act like assholes and name things immature sexual names.
There was no point here. He was just lashing out at something he's afraid of and frustrated by. Asking that people act nicer does not make something a "politically correct thought police 'safe space'". And claiming that asking that people act nicer is "co-opting of male spaces" is a pretty pathetic attempt to play the victim card while simultaneously trying to exclude and marginalize women who have contributed tons to the tech industry.
Dismissing someone by comparing a man who is asking for there to be less sexualized and derogatory language in a community to "women who want to make it all about their vagina" is nonsense on several axes. For one, the person he was attacking is a man. For another, the whole point of the argument is for it to be less about vaginas, or other sexual differences. Bringing up sex (and especially in violent and derogatory terms, like rape-me and recursive_pimp_slap) can make an environment uncomfortable for people who already feel marginalized in a community.
>What he said about women trying to make a progressive movement all about their vagina?
It's an outburst. So what? Maybe it's humor, maybe he has some kind of pathological issue with women. It doesn't matter because there is a valid point being completely ignored so people can moan about how "women unfriendly" the post is.
>What is that even supposed to mean? How is the ruby community a "progressive movement"
Firstly, I don't think the Ruby movement is progressive, mostly because it's a shitty language. Secondly, the point is not whether Ruby is or is not progressive. Even if you accept that it's a retrogressive movement his point stands because it is a general one.
>There was no point here. He was just lashing out at something he's afraid of and frustrated by.
I beg to differ. There is a real trend of PC activism aiming to protect sensitive little flowers of various kinds against offense. Your attempt to psychologise the guy is just a cheap tactic to avoid this point.
>Asking that people act nicer does not make something a "politically correct thought police 'safe space'".
The hidden (and incorrect) assumption here is that this is unconnected to PC activism.
>And claiming that asking that people act nicer is "co-opting of male spaces" is a pretty pathetic attempt to play the victim card while simultaneously trying to exclude and marginalize women who have contributed tons to the tech industry.
"Pathetic", "margenalize", "afraid", "exclude", etc. And you say this is unconnected to PC activism? His post didn't marginalize anyone. It was making a fairly specific point that your defense mechanisms are preventing you from seeing.
I'm not attempting to "psychologize" the guy. He made a flat-out misogynistic comment. I don't know anything more about him than that (well, and the other comments which have been quoted on here). But it only takes a single comment of someone calling someone else a "nigger" in an attempt to demean and exclude them before you can call someone a racist. The same is true here; someone who claims that asking that people be a little more sensitive means that women want to make it all about their vagina is clearly lashing out in the same way.
The hidden (and incorrect) assumption here is that
this is unconnected to PC activism.
I'm not even sure what "PC activism" is supposed to mean any more, or why people consider a lot of things they accuse as being "PC activism" to be negative. Most of the times I've seen it thrown around recently were when people were just asking that other people act more nicely. Apparently asking people to act nice is now "PC activism".
I will welcome debate about how much needs to be codified; I hate policies that say "you can't use these X words" as the next guy. But a lot of what people rail about as being "PC activism" is just like this; asking that people be a little more considerate in naming package they're putting into a public repository.
So, what's an appropriate reaction to this post? Maybe to say "OK, listing 'hoe' in there is overkill, that's just being used as a pun on 'rake'." Or maybe saying "hmm, I'm not sure how useful it is to ask people to be nicer while calling them assholes."
What's not an appropriate reaction? Talking about vaginas and male spaces and banning someone who just made a request to be nicer and listed a few examples of the kind of behavior they were talking about.
Yes, you speculated on his mental state quite extensively. Quoting you: "He was just lashing out at something he's afraid of and frustrated by."
>He made a flat-out misogynistic comment.
Sorry, he did nothing of the sort. He made the astute point that women tend to co-opt spaces established by men using activism. Do you deny this?
>Apparently asking people to act nice is now "PC activism".
Nope. Again, it's not just "asking people to be nice", it's a concerted, long-term effort to insert PC memes under the guide of being a nice person.
>But it only takes a single comment of someone calling someone else a "nigger" in an attempt to demean and exclude them before you can call someone a racist.
Nope. People say all sorts of things in anger, and this kind of thinking is exactly the kind of PC stupidity that is becoming a concern.
>Talking about vaginas and male spaces and banning someone who just made a request to be nicer and listed a few examples of the kind of behavior they were talking about.
What's your point here, exactly? That his ban was too harsh? Got anything to say about PC activism (you know, the thing that we were talking about)?
>So, what's an appropriate reaction to this post?
Oh, piss off you moist wanker. Did you stop to think that maybe it's not your job to tell other people how to communicate with others?
Do you really honestly think the way in which you communicate with people has no impact?
I completely agree, as a white dude having to worry about the way in which people receive my communication is just so unfair. I mean I call one guy a nigger and all of a sudden I'm racist. I'm not, I was just angry. Admittedly angry enough to call on centuries of historical context and language coached in violence to point out the lower social status of someone. But that's not racist.
It's not your job to tell people how to communicate with others. But it entirely your responsibility to communicate with people in the way they wish to be communicated with, if you want to be heard. This isn't about being PC, it's about not being exclusionary to 50% of the population. Women are not going to want to work with you if you're not willing to be inclusive.
Piss off you moist wanker. Did you stop to think that what you consider PC, other people might consider legitimately offensive? Did you ever stop to think it's not your job to tell women what they're allowed to be offended by? It's honestly pretty impressive that you consider someone expressing their discomfort with sexist language to be worse than the sexist language itself.
Misogyny is not necessarily hating women, but can also mean fearing, disliking, distrusting, and otherwise treating women as fundamentally different and inferior to men.
Claiming that a man asking that people not be immature assholes means that "a progressive movement is being coopted by women who want to make it about their vagina" is pretty much a textbook example of misogyny.
Claiming that software engineering is a "male space" (so, what, do that make the female software engineers I work with some kind of intruders on my "male space"?) is also a textbook example of misogyny.
What is it going to take for you to accept that this guy is a misogynist? Actually physically harming women? There are a lot more ways to spread fear, distrust, and hatred than just physical harm.
Sorry, misogyny means hating women. Perversion of language won't help you. Also, I don't care if the guy is a misogynist or not. There are plenty of hateful people in the world. I hate lots of people (women are nice though). What I do care about is the fact that his _post_ has had a label thrown on it to neutralise it when it contains a valid point. You've imbibed too much Kool-Aid, my friend.
Sorry, misogyny means hating women. Perversion of
language won't help you.
We don't speak ancient Greek. In modern English, misogyny means hatred, distrust, contempt towards women. Reacting to a post from a man asking "could we be more respectful and inclusive of others" with something about being "coopted by women who want to make it all about their vagina" definitely expresses a distrust and contempt towards women.
Of course, you can always parse semantics apart and say "well, he didn't say all women". That's not the point; misogyny doesn't require that you qualify all hateful statements to include every woman in existence. But that quote, in response to a man asking if we could be nicer and more inclusive, definitely states a fairly contemptuous attitude towards women.
when it contains a valid point
It has no such valid point.
No one is coming into the Ruby community, or the programming community, and trying to make it "all about their vagina". In fact, they're asking the opposite; that there's less emphasis placed on their vagina, and more on their code.
And calling programming a "male space" is inherently exclusionary. He is dismissing in one fell swoop all of the women who do code, who are part of the community.
Asking that people be nicer, and maybe consider the effect that gems named "rape_me" and "retarded" might not really reflect well on a community, with a defensive knee-jerk reaction about "politically correct thought-police safe spaces" is not a "valid point".
Yes, and I'm sure where you come from "micro-aggressions" is a real word too.
>And calling programming a "male space" is inherently exclusionary.
No, it's a statement of fact. The US Marines is a male space. Oops, am I a bad little misogynist now?
>Asking that people be nicer, and maybe consider the effect that gems named "rape_me" and "retarded" might not really reflect well on a community, with a defensive knee-jerk reaction about "politically correct thought-police safe spaces" is not a "valid point".
Yes, it is. If it's invalid, then by all means invalidate it for me.
>No one is coming into the Ruby community, or the programming community, and trying to make it "all about their vagina". In fact, they're asking the opposite; that there's less emphasis placed on their vagina, and more on their code.
I don't hang out with Rubyists. I don't care about Ruby. It's a bad language, for a start. In the general programming field there are plenty of people spending lots of time trying to boost the status of women and institute PC memes. Do you deny this?
Yes, and I'm sure where you come from "micro-aggressions"
is a real word too.
Not really sure where you got that. I didn't use that term and neither did the author of the original post. It's a perfectly valid English construction; whether the term it describes is something that's particularly relevant is another question.
No, it's a statement of fact. The US Marines is a
male space. Oops, am I a bad little misogynist now?
There are women in the Marines, and many of them have served and died in the line of duty in Afghanistan and Iraq. So not only is that not a statement of fact, it's also quite insulting to those women who have put their life on the line for this country.
Now, it's true that as of now in the US, women have not been put directly into combat roles. Combat battalions are still exclusively male spaces. Of course, that doesn't mean that women haven't been involved in combat; sometimes they have by accident, or in many cases they have through loopholes or trial programs like the Marine Corps Lioness's program.
Stating that the programming profession is male dominated is a statement of fact. Stating that people are trying to "co-opt male spaces" by being more inclusive of women is misogynist. Talking about co-opting male spaces implies that it's something that men have the right to and women to not; that something is being taken away from men by making it friendlier for women to join. That implies that either women in the space are bad, or being friendlier and making them feel more comfortable is bad, either of which can accurately be described as misogynist.
Yes, it is. If it's invalid, then by all means
invalidate it for me.
Thought police must be, well, police. Even if you want to speak metaphorically, they must be someone with some kind of coercive power to apply rules that are designed to shape how people think.
The original author was simply pointing out some examples of bad behavior, and saying "hey, this doesn't make you cool, it makes you an asshole". He mused about whether RubyGems should ban them, but then said this was unrealistic.
On the other hand, Aaron Ashworth threatened to and then did ban him from the Ruby Facebook group. So if you're looking for "thought police", that qualifies more than criticizing some people for childish names.
So, I've invalidated the point. Will you now admit that the point was not valid, and that the nasty behavior (accusing women of making it "all about their vaginas") was simply nasty behavior for the sake of being nasty, and not because there was a valid point?
And don't try to tell me something along the lines of "well, maybe he didn't have a valid point about this particular post, but it is a real problem." If you want to discuss real problem, you should discuss real problems, not lash about about vaginas and thought police.
I don't hang out with Rubyists. I don't care about Ruby.
It's a bad language, for a start.
Sure, let's forget about Ruby for the moment.
In the general programming field there are plenty of
people spending lots of time trying to boost the status
of women and institute PC memes. Do you deny this?
There are some people spending lots of time trying to boost the status of women, yes. I'm not sure I'd say "lots of people" relative to the size of the community. Most people mind their own business and don't really act one way or another. Some people act aggressively negatively. Some people act more dismissively negatively.
I have no idea what you mean by "institute PC memes". The phrase "PC" is thrown around to refer to so many things, and tar so many thing with whatever bad reputation that it's supposed to have, that I'm never really sure what people mean when they say it any more.
Some people try to institute policies to make male-dominated spaces more friendly to women. Some people try to use social means, of speaking up about what they find to be unacceptable behavior. Some focus on encouraging and mentoring women.
But none of these are about making anything "all about their vagina". That's a ridiculous reactionary overstatement. The original post wasn't about anyone's vagina, it was about wanting to take the focus off of things like that and put it onto more constructive things.
Making this argument is like making the argument that any time you bring up some men's issue, it's "all about your dick." No, actually. Both women and men are a lot more complex than just their most distinctive sex-linked anatomical features. But saying that is a great way to dismiss any concerns that there might be some kind of sexist behavior going on, because obviously if you complain about sexist behavior you must want to make everything be about your vagina, right?
So, what would you prefer? Would you prefer fixed lower bandwidths; everyone gets exactly 1 Mbps all the time, for the same price you're paying now for 50 Mbps? Then you're going to have a ton of bandwidth going unused all the time, while everything will load slower.
Or would you prefer the famously unpopular bandwidth caps and overage charges?
Saying "unlimited bandwidth" but selling it as a residential (ie, non-commercial) plan seems like a fairly reasonable solution to the problem. It gives actual non-commercial residential customers what they want, the ability to have spikes of high bitrate transfers without having to worry about overage charges or being throttled, while actually allowing that pool of bandwidth to be shared reasonably fairly.
The problem is if you divide shared resources like upstream bandwidth (or in the case of hosting, resource like disk or RAM) in precise amounts such that you could support 100% of the capacity you sold at any time, you would be wasting the vast majority of your resources. Most customers can't predict in advance exactly how much they need, and are quite averse to any kind of overage charges.
Now, for some (mostly business) customers and workloads, precise metering works well, and for some completely dedicated bandwidth works well. But for the average residential customer, who has extremely spiky bandwidth demands and is quite averse to overage charges, neither of those work well.
I would prefer minimum service guarantees rather than maximum usage allowances. If I want to maximize my use of my connection, the only thing my ISP should do is reduce my throughput when someone else is trying to check their email, so that I do not get in their way. Other than that Internet connections should be a free-for-all.
The real problem here is that ISPs are so grossly overselling their networks' capacities that they cannot provide any guarantee beyond dialup speeds unless people take turns. Rather than admit this, they try to assign blame to people who foolishly think that "Up to 20Mbps!!!" means "up to 20Mbps" when in fact the ISPs want it to mean "up to 20Mbps in occasional short bursts, and only for the things we think you should be doing."
I am not asking for commercial-grade service. I am asking that my neighbors be able to stream videos while I am seeding Debian torrents. Nobody expects some kind of Internet-connection-utopia, but it is not wrong or unreasonable to expect to be allowed to use my Internet connection as I wish, particularly when I am paying more and receiving less than my overseas friends.
Following the thread here, I think what you are asking for is unreasonable given the current infrastructure or massively unpopular.
In the current environment what you are asking for is completely possible. Comcast will give you your speeds, but if they see you are seeding your debian torrents for too long, they will throttle your connection. Now they could advertise this, but we know how unpopular connection throttling is. However in a way, a connection throttle is your minimum service guarantee - your speed will never go below the throttle.
Now I don't know anything about laying internet pipe, but lets say we gave everyone minimum service guarantees, how much do you think that would cost, and how much would you be willing to pay for a given speed? It may be completely possible that Comcast is fine with your seeding as long as you limit your speed to percentage of that number.
This doesn't really refute your point, but given these two constraints its easy to see why ISPs may choose to go the "up to XMbps" route rather than the "minimum allowed route." Would it really change anything for you if you found out that your minimum service guarantee was 768kbps at your current price point?
"Now I don't know anything about laying internet pipe, but lets say we gave everyone minimum service guarantees, how much do you think that would cost, and how much would you be willing to pay for a given speed? It may be completely possible that Comcast is fine with your seeding as long as you limit your speed to percentage of that number."
I think the cost of providing such a guarantee depends on the guarantee, and therein lies the problem. Right now, I suspect that a typical cable modem connection would only be able to guarantee dialup speeds, due to how massively oversold the bandwidth is. Of course, most people do not seed torrents or run web servers or whatever else on their home connection, and so we never see service so degraded.
"Would it really change anything for you if you found out that your minimum service guarantee was 768kbps at your current price point?"
Sure: I would have a much higher opinion of my ISP. Frankly, I would have a higher opinion if service classes were based on such minimum service levels rather than maximum levels: I would much rather pay for at least 768kbps than at most 20Mbps, particularly if "at least 768kbps" meant "at least 768kbps, and higher throughput when available."
If you want minimum service guarantees, buy a dedicated line. They generally run somewhere around $2500 a month for symmetric 50 Mbps.
If you don't want to pay that much, but you still do want the option of bursting to 50 Mbps (or more), shared bandwidth, like you get from your average residential plan, is your best bet. And I don't know about your experience, but more often than not, I do get the advertised speeds, at least when I'm connecting to servers that can support that sort of bandwidth.
I mean, I agree with you in theory, it would be great to be able to get dedicated symmetric 100 Mbps for $80 a month; but it's just not economically feasible.
And I agree that ISPs discriminating based on type of traffic (torrent vs VOIP vs HTTP, etc) is not good, but this whole thread is about Google changing from "you can't host servers" to "you can host servers but only for non-commercial purposes", which is, I think, a huge improvement and fairly reasonable given that commercial use tends to be very different than residential use and it doesn't make sense to treat them the same way.
It's not that I want a guarantee of 50Mbps. What I really want is for everyone to have a guarantee of, say, 768kbps, so that when I am sitting here seeding Debian torrents I do not have to worry that the old lady living next door will not be able to video chat with her grandchildren. I also find it somewhat difficult to accept the idea that no such guarantee will be made, yet I will still be punished if I reduce the quality of service for my neighbors -- either there is a guarantee, in which case I should be throttled in a way that ensures everyone enjoys at least that service level, or there is no guarantee in which case consuming lots of bandwidth is simply rude (but not something that should be punished).
Frankly, I think this solution is not so bad: I get lower priority as I consume more bandwidth, until I am getting only the minimum throughput for my service class. Thus people can still get their burst speeds, and I can still seed torrents or run a web server or whatever else.
My real point is that I do not see why people should be punished for using their connection continuously. Comcast did not offer me "burst service," they offered me "always on" service with "speeds up to X." I feel little sympathy for an ISP that massively oversold service and then claimed that it is abusive for customers to actually use what they are paying for.
It's actually pretty difficult, technically, to provide you with a minimum guaranteed amount of bandwidth, without simultaneously limiting everyone else.
The problem is that there are many layers in the networking stack which interact in complicated ways. TCP congestion control algorithms and TCP slow start, which happen at the endpoints. Buffering, which happens at pretty much every intermediate hop in the path. And traffic shaping, which can pretty much only drop packets to limit bandwidth used.
If I'm supposed to guarantee you 768kbps, that means that I need to drop any packets from everyone else that exceeds the capacity minus 768kbps. But if I do this for everybody, I'm back to the case where I'm giving everyone a dedicated 768kbps, and they aren't able to share excess bandwidth at all.
Now, you could imagine a scheme in which I don't limit other people's bandwidth until you actually start using some. But then if it's congested when you start your transfer, you won't actually be able to send data at your full 768kbps at first, so TCP congestion control will kick in and limit you to less than that. So when traffic shaping looks at your stream, it sees something less than being used. Should it then limit everyone else such that it guarantees you your full 768kbps? If it does that every time someone uses their connection, then services that trickle just a small amount of data will essentially guarantee that everyone is always being guaranteed their 768kbps by limiting everyone else, and you're back to the "OK, now everyone has a dedicated 768kbps connection that won't go faster".
Or should it limit everyone else based on the bandwidth that you are currently using? Say, when it notices that you are sending 10 kbps, it throttles everyone else down to allow you 15 kbps; then when you increase to sending 15 kbps, it throttles everyone else down to allow you to send 20 kbps, and so on, until you hit your guaranteed bandwidth. Based on the delays it takes for TCP congestion control to ramp up the speed it tries to send while traffic shaping ramps up the amount it's limiting everyone else to give you the bandwidth you need, and the latencies involved (generally tens to low hundreds of milliseconds round trips) it could be a few seconds before you are actually able to get up to your guaranteed bandwidth.
But those first few seconds are generally the most crucial to be delivered quickly. Most people are browsing the web, where there are lots of short page loads. You want those to be able to kick in quickly and then be done with.
Remember, this is an industry where we've only recently come to understand the effects of buffer bloat on performance. Effective quality of service guarantees, other than giving everyone X guaranteed bandwidth by limiting everyone else to the total minus X bandwidth (which, when the network approaches capacity, becomes not much different than giving everyone an X bandwidth dedicated line), is a hard problem.
My real point is that I do not see why people should be
punished for using their connection continuously. Comcast
did not offer me "burst service," they offered me "always
on" service with "speeds up to X." I feel little sympathy
for an ISP that massively oversold service and then claimed
that it is abusive for customers to actually use what they
are paying for.
Yes. It's always on service (as in, you can be connected and have the service available 100% of the time) and have speeds up to X available. That's what they promised, and that's what they deliver. They also sold this as a "Residential" service. They have other services for commercial and dedicated lines, that they will sell you for greater utilization.
You are not paying for continuous use of X, you are paying for an always available line that gives you speed up to X, for personal residential use.
Restrictions on not using the network abusively or not running commercial services on a home network are not some creepy abusive plot, they are really the best that the networks can do to provide you with affordable, high-speed broadband.
Do I wish that there were more competition? Sure. Do I wish that I got higher speeds for cheaper? Sure. Do I wish that they would be network neutral and not block ports running on my network? Absolutely. But there's absolutely nothing wrong with selling a residential plan that is for residential purposes, and enforcing that, separately from their commercial plan, and separately from their dedicated plan. It's not that difficult; if you want to use it for commercial purposes, use their commercial plan. If you want guaranteed bandwidth, buy a dedicated line.
And remember, the ISPs have not "massively oversold" their services. If you look at the FCC's report (measured in 2011): http://web.archive.org/web/20130511164730/http://transition.... , you'll see several ISPs that actually exceed their advertised bandwidths even during peak hours. Now, some of them are clearly not doing so well by that metric; Century Link is not even hitting 80% off peak, and barely 50% on peak. I would say you have a good case for false advertising there. But if you notice, Comcast and Verizon FiOS manage to exceed their advertised bandwidth, on average, even on peak. This matches pretty well with my experience over the last 5 years or so. I've had both DSL and Cable. DSL routinely underperformed what was sold, which was already paltry. But cable has generally exceeded what was sold, when connecting to servers that could actually handle the load.
So, I'm not sure I'd call that "massively overselling", other than maybe Century Link (and the other DSL providers don't hold up too well either).
Think of it like a buffet. For efficiency and simplicity, it's an all-you-can eat plan; unlike food, people aren't very good at knowing how much they are going to use and so charging based on usage is much more unpopular, making buffet style plans much more populat. So they do "all you can eat". And the rules are, it's all you can eat, and in one sitting; you can't take a bunch with you and then sell it to someone else, nor can you horde food for takeout because "you're going to eat it later". Would you start complaining and railing that the all-you-can eat buffet massively overselling? No. That's all that they're doing with the internet plan; it's just that there are less social conventions and it's easier to accidentally (or deliberately) massively overuse your fair share of bandwidth than it is to massively abuse a buffet, since it all happens automatically.
I would prefer truthful advertisement. If they must cut down on minimum transfer rates, then that’s what the advertisement should say.
I have a general rule: Buy 250KB/s, and you get 100% of the bought speed.
Buy 1MB/s, and get 95% of the bought speed.
Buy 10MB/s, and get 80% of the bought speed.
Buy 100MB/s, and get in average around 50% of the bought speed. 25 at prime time, and 90 around 4am.
In the end, more expensive connection give you more, but each level give less proportionally bandwidth than advertised. This should be illegal. If they want to sell me 25MB/s, but at strange hours up to 100MB/s, than the advertisement should say so, plain and simple.
If you went to the gas station and only got 50% from paying for a full tank, you, me and everyone would be angry. It wouldn't matter if the gas station was "low" on gas, or if it meant that the gas station might end up with no gas left for the next customer.
Bandwidth is not like gas. It's not something that you buy, and consume it, and then go out and buy more.
Instead, there's an infrastructure that need to be built. That infrastructure has a certain capacity; at any given time, only so many bits per second can be flowing over it.
Now, most people don't use all of their capacity at a continuous, constant rate. Rather, their usage is quite bursty. You use a lot of bandwidth for a short amount of time when loading a video, and then none while you're watching it. Or you use lots of small bursts while surfing the web.
If they sold 100 Mbps (no one sells 100 MB/s) and guaranteed that to you, it would be astronomically expensive. But selling you service that gets 100 Mbps in bursts if people have average personal-use utilization patterns is perfectly possible.
Now, how exactly should they advertise that? That's a tough question. If they were going to advertise the minimum guaranteed bandwidth, it would be laughably low (and of course, they could never really guarantee any minimum, since how much bandwidth you get for a given transfer depends not only on your connection, but the backbones in between and server's connection; there is no way to guarantee any particular amount of bandwidth in any meaningful way). And you would almost always get more than that, so that would be a fairly meaningless number.
Perhaps they could advertise an aggregate average bandwidth? That would be pretty hard to define and test (what sample period are you measuring over? How do you know when a transfer has stalled due to congestion somewhere vs being finished?), and wouldn't really give you much meaningful. Are you really going to go out an canvas your neighbors to determine if your neigbhorhood really is getting the promised average aggregate bandwidth?
The only really meaningful thing they can give you is what the actual maximimum bandwidth they will allow over your connection. That is a hard and fast number, and can be tested fairly easily. Of course, that doesn't say much about your bandwidth accessing any particular site, but there's nothing you can really do about that without control of the entire network.
Now, actually in practice, it appears that when I buy a certain level from Comcast, they don't actually use that as a hard maximum. I've seen bursts that were higher than the advertised bandwidth; and of course, I've seen transfers that were lower.
I know that everyone likes to criticize ISPs, and there is definitely some behavior that I find odious (blocking particular protocols, attempts to subvert net-neutrality). But over-selling bandwidth is not one of them. I can't really imagine a system that would work better than over-selling bandwidth.
I don't have any problem with an ISP saying "up to #Mbps" as that's what they allow each customer to get (though this is 2013 and I'm sure with the amount of metrics that CPE can gather, we could measure average thruput and advertise that too).
What I have a huge issue with is selling the services as unlimited and then smacking people down when they walk over some invisible line, or worse selling an "up to #Mbps" line when they know damn well based on basic math that nobody's ever going to get anywhere near that speed in that area.
It's absolutely ripe for abuse. You, as an ISP, can legally sell someone a 100 meg line you know in advance won't reach that speed.
If they has such hard time to measure limits, they can always use first hop router as test base.
But lets take the look from the buyer. You see a 8MB line for $80 amount, and 10MB line for say for $100. Knowing what you pay for is the minimum requirement for informed purchase, or you end up with a lemon market.
ISP are lemon markets, and you get poor quality for more expensive price. No amount of "The infrastructure has a certain capacity" argument is going to change that.
I'm not sure what would be preferable. They could sell you metered bandwidth; but everyone always complains about metered bandwidth, and no one wants to accidentally have their 14 year old nephew who comes to visit for a week blow out your caps and cost you tons of money because they left Bittorrent seeding a bunch of popular movies.
They could just sell you lower bitrates. But then everyone would suffer, as they wouldn't get the short bursts of quick bandwidth they need to browse the web or download files.
Or they could do what they're doing, which is sell under separate residential and business plans. The residential plans are sold under the assumption that you'll be using them for ordinary personal use by you and your family, and that you're not going to build a data center in your basement and start reselling bandwidth to people colocating servers in your basement.
"Business" and "residential" have fairly well established meanings. There are already plenty of zoning laws that make business vs. residential, or residential vs. commercial vs. industrial distinctions. Selling a residential plan that includes in its terms of service "you may not use this for commercial purposes" is not unreasonable.
Now, I do object to residential plans that unilaterally block ports without recourse, or disallow any running of "servers", as there are lots of valid reasons why someone would run a server for personal, as opposed to commercial, purposes. But I can't find a good way to allow everyone to share a larger pool of bandwidth at a lower price for home use, without allowing some people to take advantage of it for profit, without making the business/residential distinction.
And sure, there will always be grey areas. What if you work remotely? What about personal uses that are abusive? These are things that need to be dealt with on a case by case basis, or spelled out clearly in the ToS. You can't really include the entire complexity of the ToS in a single ad, so I'm not sure you can claim false advertising just because there are a few terms in the ToS which weren't unambiguously stated in any "advertising" about the service.
Really the only difference between "residential" and "commercial" plans should be service guarantees. I do not expect Comcast's residential cable service to have any particular guarantee of service; if I had a commercial contract, I would certainly demand some sort of guarantee about available bandwidth and uptime. That is what we have now, more or less.
To put it another way, suppose nobody gets any service guarantee with their residential connection. Why should it be acceptable to say, "How dare you maximize your use of this, when it reduces availability for everyone else?!?" Nobody gets a guarantee of service at all.
Now, if we do get guarantees about our minimum service level, then there is an easy solution, which is to just reduce throughput for "heavy users" to the point where everyone else is getting their minimum guaranteed service. That would not be so bad at all: minimum service guarantees rather than maximum service limits. Of course, once you start making guarantees like that, people start expecting you to follow through and your ability to grossly oversell your network's capacity is constrained (what a tragedy).
So, let's think back to the analog, circuit-switched telephone network. If you have a telephone line, you generally expect to be able to make a call at any time. But for anyone to be able to make a call at any time across the country, you would need to have one cross-country line for each person on the side with lower number of people (assuming, of course, that you divide the country in half and need to run cross country lines between the two halve; bear with me, this is a bit of a simplified example).
Of course, if you built one line for each person, then the vast majority of them would go unused. It would be completely ridiculous to overbuild like this; everyone would be paying for a ton of capacity that's unused. So how about if they build it to comfortably cover 10% more capacity than they've ever had used in the past. This allows for enough headroom for spikes, and when usage starts crossing that line they know that they need to start building out more capacity.
But of course, then some disaster strikes, and everyone tries to call their loved ones at once to check in on them. Usage surges to more than 10% higher than their previous high, and they run out of lines. Oops, now they've violated their "minimum service level". So, should they only have sold you long-distance service when they knew that there was less than one line per endpoint? Well, sure, it would have been ridiculously expensive and you wouldn't have bought it to have your own dedicated line the whole way across the country.
Now, the considerations in a packet switched network aren't all that much different. You can be more efficient about sharing the same resources because you can even share a single line, with several people sending packets at different times. But if you want to provide some kind of guaranteed minimum service, you need to take whatever you most limited path is, and divide up its cost and bandwidth between all customers who could possibly use it simultaneously. And I guarantee you, that will add up to paying a fortune for a pittance of bandwidth.
Why should it be acceptable to say, "How dare you
maximize your use of this, when it reduces availability
for everyone else?!?" Nobody gets a guarantee of
service at all.
Because if they do that, people will start leaving that service, saying "it's slow and glitchy, this other service gets much better ratings on SpeedTest.net and all of my friends on this other service say it's more reliable for them", when the reason for that is "this other service" actually has an enforces a ToS against abusive use of the network.
Does anybody get a "guarantee of service" to the public roads? Then why should anyone complain if someone else decides to run a private parade on those public roads, blocking everyone else? Or should we all get a "guarantee of service", and then deny anyone the right to have a parade ever?
Sometimes, you need to share resources without precise, hard and fast constraints, but instead based on social conventions, definitions of completely egregious behavior, and consequences for that completely egregious behavior.
Well metered connection - the problem is the pricing. 10USD per month for contentedness + $1 per terabyte seems like a good deal. And even if my nephew decided to download all the porn of the internet he will run out of space before I run out of money.
Taking a look at their "idea" page, I found myself nodding along with most of their bullet points (or shrugging and saying "not exactly my preference, but I can see why you'd want that"), until I hit:
Ghost would have cut-off points with major versions,
allowing core developers to remove old code from the
codebase and evolve the platform to allow it to improve.
No one expects an app written for OSX 10.4 Tiger to work
on OSX 10.8 Mountain Lion.
Oh, hell no. Backwards compatibility is way more important than some shiny new feature. When I upgrade my software, I expect it to work better, not break. If I have a working plugin from 5 years ago, why should I have to fight with some pointless API redesign just to get it to work again?
In the real world, people need compatibility more than they need whatever cleanup you're able to do by breaking compatibility. Heck, in many cases you can get both by doing your rewrite but leaving a compatibility layer on top that gives you the compatibility that you need.
I'm so sick of trendy "modern" frameworks like Rails that break compatibility every 5 minutes, and listing breaking compatibility as a major feature is a huge turnoff.
How about focusing on spending the pre-1.0 releases iterating and designing a really good API that will be amenable to backwards compatible extensions, and then sticking to that API and backwards compatible extensions to it for the forseeable future?
How long do you expect upgrades to work before a break in compatibility?
Forever? At least the linux kernel has an explicit goal of never breaking userspace. That doesn't mean other parts of userspace don't break themselves, but the linux kernel has as a development goal to never break binary compatibility for userspace.
It's important to remember that the Kernel is a very small piece of the puzzle that decides whether your 1991 binary works on a system today. The real kicker is whether the glibc versions match, whether X11/Motif will still be around for a while, etc.
But I still admire the kernel for their stance even if it can't solve every compatibility problem.
My last computer retired - 1 month ago. It was more than 5 years old, running Windows XP. XP is still very popular and I would expect it to still be supported and it's 12 years old.
Where did you get your 7 year magic number from?
You can't talk about Windows XP like it's a single, fixed point in the release cycle. XP was released in 2001, giving you your 12 year number, but there were also major service packs released in 2002(SP1), 2004(SP2) & 2008(SP3). The last release of XP was only 5 years ago - more recently than OS X 10.4
Of the new software that still claims XP compatibility, much of it requires SP3.
Yes, it's free but that doesn't mean it's painless. Going to SP2 and SP3 broke backwards compatibility with some drivers and software. It increased the RAM/CPU requirements for running the OS comfortably. They weren't just harmless stacks of collected bug fixes.
Microsoft products receive 5 years mainstream support and 10 years extended support. XP is currently supported for organisations who purchased extended support, but only because there was extraordinary demand for it. It ends in just under 6 months from now.
Unless you're a large organisation paying a lot of money, you aren't likely to get 5 years of support for a particular version of most products.
Especially for a young project, I think this is ok. You don't want it to be set in stone too early. Once there is an established ecosystem around Ghost, there will be a lot more pressure to keep it stable.
Even better than that is pressure to keep addons/plugins/whatever up to date.
I think there's some good precedence for that with Firefox who (still?) deliberately broke all their extension compatibilities on every release, and contrary to that Wordpress who've led to a fully automated exploit ecosystem.
I don't know about Firefox doing that on purpose, but the addon that I've written (Link Exposé) has seen several releases of firefox (19.* to 24.*) without having to do an (api) "update". It's written using the new jetpack SDK (now "Add-on SDK") - and there is a commitment to keeping that api stable.
Nope, this is exactly what happened to Wordpress. As a senior Wordpress developer who deserted the platform after giving up, I can safely comment on your views:
#Supporting older versions is a pain. Supporting all features in older versions AND newer versions to work together is an even bigger pain. Example: Wordrpress.
#Compatibility for older version leads to bloated code, with too many legacy variables, too many points of failure. Example: Wordpress.
#Evolution of any software requires that it discards old ideologies and embraces the newer ones. The ones that don't do, tend to drift away from the main goals. Example: Wordpress.
Wordpress was started with the exact same intention as Ghost and yet, what you are left with now is a half-baked unstable CMS, and a half-baked blogging platform that breaks old plugins with each upgrade.
If you want to embrace progress, then you must embrace C.H.A.N.G.E. And this is not just for software.
That's hilarious, it's a major feature I want from a blog and I came to the comments to advocate. It's one of the best things about Drupal, for instance.
I want a frozen codebase that only worries about critical security updates.
In the real world, you will break your site by adding new plugins every few months. The site will break. I get a stable codebase and I sit on it.
Development causes bugs! Milestone releases are what I want.
> In the real world, people need compatibility more than they need whatever cleanup you're able to do by breaking compatibility.
Here's the thing: if you're a user that needs compatibility don't upgrade! (not an option with most blogs) If you're always adding new functionality and plugins to your blog, things will break. If your business needs constant new web technology updates, use a real CMS and fix them when they break. They will break, they always break.
Compared to WordPress, which touts backward compatibility as a strength, yet still manages to break itself in some way, shape, or form with every new release?
I'm not necessarily comparing to WordPress. What I'm saying is that they should be going in the other direction; towards better backwards compatibility.
Of course, one way to achieve this is less reliance on add-ons, so you have less API surface to expose. Having a usable WordPress install relies so heavily on add-ons that it's kind of pointless to consider WordPress alone.
> In the real world, people need compatibility more than they need whatever cleanup you're able to do by breaking compatibility.
Time and time again, rolling software has proven to be more secure than static releases. A plugin from five years ago that hasn't been maintained in that time is probably going to hurt you a lot.
Rolling software is better achieved with better backwards compatibility than it is with constantly breaking API changes.
When you have constantly breaking API changes, and then someone has an essential plugin that's unmaintained, then they're a lot more likely to stay with your old, buggy, insecure base package, rather than finding someone who knows how to update their plugin (remember, most users aren't programmers, and most have installed plugins for a reason).
What you do is try to minimize the API surface that plugins have so it's easy to maintain backwards compatibility, and minimize the impact that older plugins can have by keeping them reasonably well isolated.
I'm not much of a wordpress user, so alas can't provide good wordpress examples, but this is really a software in general thing. Run a Linux box? How many times have you upgraded OpenSSL in the last five years?
For that matter, most apps written for Tiger should work on Mountain Lion, with the important exception of PowerPC apps - but that was a matter of maintaining library support for an entire architecture, and anything written for the Intel release of Tiger is fine.
The other way around is different, of course, as as a huge number of new APIs have been added since then.
Should Apple not have gone to a 64-bit operating system because of hardware like the first MacBook Pro, with a 32-bit processor and RAM that maxed out at 2GB?
This is the reason why my own blog is static files of Markdown for the content, combined with a tiny blog engine, all in the same git repo - I just don't want to deal with the pain of some upgrade suddenly breaking stuff I've come to depend on.
I'd be curious - what do u use, and why? I've been meaning to look into getting my own blog restarted, but just haven't gotten down to the question of which static site generator to use.
More than $300,000 was raised on Kickstarter for Ghost, so after seeing this public release of Ghost I was really surprised. It is so simple, I could have paid a developer $500 to make it with more features.
The Ghost admin panel doesn't allow editing themes, the post doesn't have buttons that allow you to quickly format posts, there are no SEO options/plugins, there is no theme editor that allows editing of themes, no sidebars, no multi-user creation, no e-mail to post, etc. Too many features are missing and this is very simple. WordPress is better, there just is no debate on this right now.
This is the first public release, to get feedback. They already stated (on their own blog) that an improvied admin panel, themes, plugins, etc. will come but it will take some time.
Also, we are talking ~37k lines of code, not exactly something you can write in a week or two for $500.
> I guess we'll never obtain a perfect alternative to the mouse.
Is that really what they're going for?
I don't think you should view the Steam Controller as the controller to end all controllers. From that point of view, I'm sure it will fail, and people will be disappointed.
Instead, it's a controller that makes PC games playable from the couch. It won't be quite as good as a mouse and keyboard for games that were designed around those. It probably won't be quite as good as a standard console controller for games that were designed around those (you don't have the physical buttons to roll your fingers over to hit particular combos quickly). But it should make both types of games playable on a single controller.
And once it's out, who knows. Maybe people will be able to design games specifically for this type of controller, and there will be some games that are best played on it.
No, V8's regex library is not written in C. V8 compiles its regular expressions to machine code at runtime. The availability of the compiler at runtime can be a liability for things like startup time or memory use, but can also be a key advantage in situations like regular expression parsing or packet processing.
You need a regex library to turn a regex into machine code. What the parent means is that the V8 regex library compiles them, while the one used in the C code merely interprets the regex.
(The C and C++ thing is just adding confusion here)
Regular expressions are part of the JavaScript language, so they're as much "written in JavaScript" as any other language construct.
The point is that a regular expression compiled by V8 (which is not written in JavaScript) is faster than a regular expression as compiled by some particular C compiler. Of course a C compiler could possibly be written to understand calls to a standard regexp API and compile those to binary.
But it does show how good V8 is at optimizing out the JS part of JS when it's irrelevant to the computation, and it shows how well-optimized the regexps in V8 are.
None of this is terribly surprising given V8's use case, but only a few years back this would have been a ridiculous result. I enjoyed taking a minute to reflect on that.
It's not JavaScript bytecode, but regex bytecode. V8 parses regular expressions to regex ASTs, takes them through some more intermediate forms, then finally to a special regex bytecode. That bytecode is either interpreted, or JIT compiled (depending of some build options, I think).
You can look at a list of bytecodes in [1], and at the x64 JIT in [2].
Reading through the responses to this comment, the upshot w.r.t regex performance is that it's a significant advantage to have native regex support in a language. Because C doesn't the regex ultimately has to be translated into C at parse time, whereas with Javascript the regex is converted to machinecode at run time.
This is similar to the advantage of abstraction layers in general, although there's a cost if you create abstraction layers for things no-one much cares about.
I'm not sure you could reasonably claim that Lavabit's private key is an instrumentality of crime, since Lavabit's private key is in the control of and used by Lavabit, the service provider, not the alleged criminal. This would be like claiming you could seize the entire phone network because someone somewhere used it to commit a crime.
Now, you may be able to demand that Lavibit hand over the user's password or encryption keys, if it is able to do so. Those could likely be considered instrumentalities of crime. But handing over Lavabit's own private keys goes beyond that, to something that Lavabit merely uses to keep it's communications private with all of its customers, the people under investigation and everyone else.
Asking for Lavabit's private key is like asking for the master key to let you into any room the building, when only one tenant is actually under investigation. It goes beyond what is necessary to investigate the actual case in question.
If the landlord uses identical locks on all the apartment doors, he can't turn around and complain that turning over the key to the apartment being investigated would open all the doors.
As for the instrumentality of the crime, even though it's Lavabit's SSL key the government's contention is that Snowden made use of it in his alleged crimes (by for example encrypting leaked data with the public half of the key for transmission to lavabit's web to email gateway, where it would ultimately be decrypted by lavabit using the private key, and then emailed to the a recipient.) Suppose a criminal rented a car and used it as a getaway vehicle and then returned it. The police could get access to the car for forensic evidence from the rental company, notwithstanding the fact that the car belonged to the rental company who was not accused of any crime.
If the landlord uses identical locks on all the apartment doors, he can't turn around and complain that turning over the key to the apartment being investigated would open all the doors.
Why?
When setting up a business, are you required to organize it in such a way that in the future, the government can come along and perform a certain kind of search/and/or seizure? It that your obligation, failing which all of your customers must suffer?
It's one thing to have a law that states the government can ask for things. But I haven't heard anybody argue that the law requires you to organize your affairs in such a way that you can comply with requests like this "cleanly."
>It that your obligation, failing which all of your customers must suffer?
> It's one thing to have a law that states the government can ask for things. But I haven't heard anybody argue that the law requires you to organize your affairs in such a way that you can comply with requests like this "cleanly."
Generally you don't have to set up your business in such a way as to comply with requests cleanly, though there are exceptions for certain telecom providers (not applicable here). But by the same token your inability to comply cleanly doesn't absolve you of the responsibility to comply.
So our landlord hypothetical the landlord certainly is allowed to use the same lock on every door, but he still has to turn over the key when it is demanded.
As for the collateral consequences to third parties the court will not assume that the government is going to abuse their access to search more than they are authorized to. That seems to be the biggest disconnect. The judge didn't think that the ability to decrpyt all the traffic was a pertinent harm because his order didn't allow the agents to look at it. Whether or not that's a reasonable assumption as a matter of fact is an empirical question, but it is certainly a reasonable, perhaps even compelled, one from a legal standpoint.
If the business is allowed to send its customers a form letter telling them that hey has given the master key to the government, I would understand the position that the interests of the other customers were reasonably safeguarded.
If, for example, one of them was discussing some business and then suspicious trading occurred, she might ask whether a government employee abused the master key and was doing some insider trading on the side.
But if the business is not allowed to tell the customers that their privacy has been compromised, I would not want to give the government the "benefit of the doubt" about their use or abuse of a master key.
Trust, but verify, as they say. How does one verify when these security letters are handed out like candy?
> When setting up a business, are you required to organize it in such a way that in the future, the government can come along and perform a certain kind of search/and/or seizure?
No you aren't required to, however, you are required to cooperate with legitimate searches/seizures even if the you have structured your business so that doing so inconveniences other customers unrelated to the target of the search/seizure.
You can't structure your business in such a way as to make narrow searches/seizures impossible without inconveniencing unrelated customers and then use that as an excuse not to cooperate with otherwise-legitimate searches and seizures.
But it's not a matter of using identical locks. He has offered to turn over particular pieces of evidence about particular suspects; but he refused to hand over his private key which would allow the feds to snoop on everything. It's like asking for the master key, when only the key to one particular room (or one particular car) would be sufficient for the investigation.
Analogies extended too far can be unhelpful, but I'll risk it one more time.
His offer, made rather late in the game, was the equivilent of the super telling the police they couldn't enter the apartment, but that he (the super) would search it for them and pick up whatever they were asking for, if they were willing to pay him some money for his time.
That might be a reasonable offer, but I don't think there's anything in fourth amendment law, or the statutes, that require the police to take him up on it, rather than just insisting that they do the search themselves.
In my own reading of the case, the area of the government's actions that seemed the weakest was the applicability of the rationale for the probable-cause-less pen-trap and stored communication act requests (i.e. the third party doctrine from Smith v. Maryland) to email headers and usage logs from a service that held itself as not being able to access these things. In that circumstance it looks to me like the user does have a reasonable expectation of privacy in those (meta)data, and so a warrant issued upon probable cause should be necessary. However, this case also involved a grand jury subpoena. That's a whole other (troublesome) kettle of fish, one that frankly I'm not too familiar with.
Yeah, comparing net worth is a terrible way of comparing wealth between individuals. Anyone who is fresh out of college with student loan debt, or who recently bought a house on a mortgage, has negative net worth.
If you're going to compare against collective net worth, then I personally have greater net worth than 25% of America, and the entire American federal government! Woo, I must be rich, right? Well, no, I've just paid off my student debt and don't have a mortgage. On the up side, I don't have any debt. On the down side, I don't have much in the way of equity, while some people with negative net worth have substantially more equity than I do, and if they, say, decided to sell their house and move to an apartment would suddenly have considerably more net worth than I do.
"Net worth" is not wealth. Measuring wealth is a somewhat difficult thing, but net worth is a fairly poor way of measuring it.
Generally buying a house should not by itself give you a negative net worth. Net worth = Assets - Debts, so when you buy a house you generally get an asset of $X (your house) and a Debt of 80% of X (your mortgage). You 20% of equity will simply be a transfer from a cash account into an asset. The act of buying a house will decrease your net worth because of closing costs but it probably won't make you go negative by itself unless you put the closing costs on a credit card.
Sorry, you're right, the value of the house does count towards your net worth.
However, if you already have some student loan debt and the value of your house declines due to the housing crunch, you can easily be in the negative on "net worth", while still having more actual wealth than someone who's at 0.
However it works out, I've seen figures citing 25% of American families as having negative net worth. But I don't think that means that they actually have negative "wealth", nor is it all that useful to point to someone who has 0 net worth and say that they are wealthier than 25% of America combined.
I think you're using "wealth" to mean "assets" which I don't think is a useful number for any of these comparisons. In the example you give where a person has a house which declined in value and some student loans, they do have a negative net worth but they are also worse off than the person with 0 assets and 0 debts.
Having the house that they need to make payments on means that not only do they have 0 or negative net worth, they also have strict cash flow requirements which the person with 0 assets and 0 debts does not have.
I mostly agree with you, but I think you're going a bit too far: Someone living on the street, having no income, would have 0 assets and might have 0 debt (until they need medical attention...).
For someone with a family, struggling to keep the house is certainly better than living on the street. Still, being in a credit crunch could of course lead to that family being evicted, so yes, negative net worth isn't great.
There may be a few extremists out there, but not many. What you see lots more are people who are tone deaf and make problems worse by going around and yelling "you're racist/sexist/homophobic", "no, you're a feminazi/PC", and on and on without ever really getting anywhere. Most of those people (on either side) aren't extremists, they're just caught in the internet spiral of hate. But just because some people go overboard on the internet spiral of hate that simply amplifies problems, doesn't mean that there aren't some real problems.
So, responding to someone who says "rape-me is not an acceptable name for a gem" with such rhetoric is instantly escalating that internet spiral of hate for no reason. Lumping people who have legitimate complaints, like "let's not have rape references in our public software repositories" or "let's try not to sexually assault people at conferences" with "extremists" is a way of dismissing those legitimate concerns and simultaneously escalating the rhetoric to the point where nothing useful will come of it.
These are two very different issues. One is a question of whether it's a good idea to chastise your collaborators so strongly on a public list, or whether there could be more polite ways to make your opinions known. It didn't really have any kind of discriminatory or sexist content, simply a question of the best way to encourage good practices and discourage bad ones.The other is somewhat more relevant. It's an example of puerile humor, in a private conversation that happened to be in a public place (at least, as far as I've been able to gather). I found that it seemed to be an excessive attempt to shame people for behavior that was, as far as I can tell, supposed to be private, but was in a public place so other people could overhear it. I think that there is some reasonable debate to be had over what kind of behavior is appropriate in a public space where you can be overheard, but that there was an overreaction to it, since it was private behavior. However, the internet spiral of hate wound up blowing the whole thing out of control, in part because there are so many people who are so sensitive on both sides of these issues, and it went way beyond anything it should have.
Here's the thing. Donglegate could have been someone pointing out behavior that she considered inappropriate, and people could have taken that to heart and moved on. But lots of people overreacted. Posting people's pictures online publicly, rather than either talking to them yourself or letting PyCon staff talk to them, was an overreaction. Firing one of the people involved in the conversation was an overreaction. Firing Adria Richards was probably an overreaction, though at that point she had shown herself to be divisive enough to not be very good at community building. Sending her death threats and calling her a slut was definitely an overreaction.
So you can see several areas here were there were massive overreactions that led to this being far larger than it should have been.
Likewise with this post, the original post was a fairly reasonable request. "Let's not have nasty, rude things like rape-me in highly public, visible, and widely used code repositories". Now, some of it may have been a slight overreaction, like mentioning "hoe" (which is a clear reference to "rake") along with these other items. But what's a good way to deal with that? Probably to discuss those specifics; say that "rape-me" and "recursive_pimp_slap" are pretty clearly inappropriate, but there's really no problem with "hoe" or "therapist", and maybe discuss his point about whether there should be an explicit filter versus applying a certain amount of judgement. Those are reasonable, appropriate ways to respond to the post, that won't lead to donglegate style escalation.
Talking about "vaginas" and "co-opting of male spaces" is, well, the opposite.
It's generally socially acceptable to express exasperation with a group by pointing out specific flaws in their arguments, offering constructive criticism, and trying to de-escalate the situation. You should also be aware when doing so of whether you might be blind to some real problem, and that your response could come off as dismissive of that real problem; so you should try to first identify the problem that is being addressed, and understand why people consider it to be a problem. Hmm. When people refer to a "safe space", they generally don't mean that no one is ever going to be offended by what someone else says. No one is going to measure out every word that they say, and always avoid stepping on someone's toes.A safe space is instead one where you feel comfortable telling someone when you think they crossed the line, that they will respect that and not attack you for it.
One thing to keep in mind is that what's appropriate in one context may not be in another. Among close friends, you may feel perfectly comfortable telling racy jokes, or jokes about Jews or Catholics or blondes or what have you. When you're in the office, or at a conference, and there are people you don't know, you should consider that they may not take those jokes the same way that your friends do.
Think to yourself. If you have to tell someone "this is not a safe space", you are basically telling them "I do not want you in this space." Because if you want them in that space, you will make it safe for them. You don't have to tell your friends that, and can crack all the offensive jokes you want with them, because you know that they will be OK with it. But if there's someone there you know will not be OK with it, and you crack the joke, then you are saying to them "I would like to hurt you." Now, there are obviously nuances; sometimes you may crack the joke and only afterwards realize that it went to far, at which point you could choose to apologize and diffuse the situation (or make another making fun of yourself, depending on the circumstances).
On the public internet, recall that you can never be sure of who will see your joke, and how they'll react to your humor. Things you post to the public internet should be things that you are OK with your wife seeing, your grandparents seeing, your kids seeing, your buddy back from Iraq with PTSD seeing, a battered wife seeing, a child victim of sexual assault seeing, and so on.
If you want to do off-color jokes publicly like that, be sure to have a thick skin, because someone's sure to be offended and start trying to escalate that internet spiral of hate. This is where Penny Arcade slipped up; I think that the original Dickwolves comic was not a bad comic and not particularly offensive; in fact, it was lampooning ambivalence towards horrible things happening inspired by game design. But of course there was someone out there who got offended, and they made the mistake of taking offense at the offense and continuing to escalate the internet spiral of hate.
Sometimes, you do need to think to yourself and say "yes, I am OK with offending you." There are some people out there who try to pick apart everything and find something to get offended about in it. If you publish something publicly, you can't ever please them. But if you do, stop for a minute and decide if you really do want to offend them, of if maybe you'd rather let them be. And if you are sure that you are OK with offending them, then be sure of it, say your piece, and be done with it. Don't try to tell them why they shouldn't be offended. Don't make fun of them for getting offended. Just leave it be and move on.
I'm curious why you call out minority rights groups. There are lots of different organizations that may have goals you agree with, and techniques you disagree with, or that you find damaging. Why do you specifically call out minority rights groups for "behaving badly"?