The actual spam and completely incoherent questions are deleted. So what you're left with is things that are actually legitimate questions, so don't merit admins intervening and deleting, but which touch a nerve in some other way; like people asking about how to send out large volumes of (presumably) unsolicited email, people asking homework questions, and the like.
Also, note that some of these "most downvoted questions" are also among the most upvoted as well, having very large positive scores, like https://stackoverflow.com/questions/1642028/what-is-the-name.... Once a question becomes famous enough, there are likely to be a number of contrarians who don't like it and downvote it, and eventually that can add up.
And then if you look in the comments of some of them, that seems to be not too bad but which have more downvotes than you'd expect, they got a downvote brigade because they complained about a few downvotes on meta. Pretty lame that people do that, but it happens.
Between these options, 1 seems the most reasonable to me. I refuse to play along with anyone who thinks that they need to hijack my computer in order to sell me content. They want my money, they can sell me DRM free content.
I wouldn't call being a teacher more prestigious than being an engineer, nor a social worker, but there are still a lot of women who are more interested in going into those fields than into engineering disciplines.
Other studies also point to other reasons; in computer science especially, there's a very strong effect of computers being seen as boys toys, so men come into the major with more experience and more interest in the field just to begin with: <https://www.cs.cmu.edu/afs/cs/project/gendergap/www/papers/s...
The gender gap in engineering disciplines, as a complex social phenomenon, is likely to have many interrelated causes. Between lower encouragement of computers as girls toys at younger ages, the fact that there is still a bit of an expectation that men will be the primary breadwinner in the family and thus women can get these lower paying but more rewarding jobs, the fact that the large existing gender gap makes it less comfortable for women in the major, in the workplace, and so on, it's unlikely that there's going to be one single cause for it.
So, in summary, while from what I found it looks like it's not prestige but how rewarding the job is perceived to be that makes more of the difference, but that's not to say that your hypothesis is wrong, just that I found some evidence to support a different effect that at least appears to be stronger than the effect you describe.
The "social expectations" hypothesis fails to explain why countries with higher living standards have more polarized sectors. The idea that in a perfect world with no "social pressure" we would reach a parity between genders ignores just about all research done on the biological gender differences.
A hypothesis about why people end up in the jobs they do fails to account for whatever non-causative correlation someone can cook up? Astonishing! Why doesn't every country with a highly gender-segregated economy have a high standard of living?
Obviously because it is quite reasonable to assume that standards of living partially cause gender distribution by making daycare affordable, allowing more paid leave, etc., whereas gender polarization would not be expected to be a strong enough effect to pull an entire economy significantly in one direction or another.
Causal modeling is a very difficult thing when you cannot perform a controlled experiment. I would be interested in your take on how you would suggest that the authors attempt to confirm or disprove this hypothesis.
Right. Precisely. Gender polarization isn't a strong enough effect to pull significantly on an economy; sputr is trying to use a spurious correlation with little value in actually predicting whether a country will have a high or low standard of living as evidence that we've all had the wool pulled over our eyes.
Assuming you mean the authors of the documentary, I'll give you a new synopsis highlighting what it's really about:
Strawman arguments abound as our intrepid documentarians drag us from interview to interview to assert that it seems people conform very closely to what our stereotypes tell us to expect of them. Obviously this must be the inevitable result of our biology! Our strawman assertion of what "equality" means is defeated! There's no way our stereotypes could be self-perpetuating! People definitely don't continue to believe in the same religions or speak the same languages or eat the same food or celebrate the same holidays just because their ancestors did! Propensity to speak English and believe in the Judeo-Christian God must also be biological destiny!
Per your last question, I have no meaningful suggestion for the authors of the video; they're going to have a miserable confirming or disproving anything as long as they insist on using logical fallacies to do so.
On the contrary, the difference in living standards explains it perfectly. If you're in a poor country, pragmatism forces you to drop your 'social expectations'. It's either earn enough to eat or hold on to your prejudices. In that environment, people lose their prejudices fast.
Sorry, but what planet are you from? Every day we're bombarded with stories and images from the developing world of men, women and children trying to make a living. Villagers migrate to cities seeking work. People work in factories and make a better wage than they could anywhere else without education. Women take micro-credit to start up little businesses like mobile phone call booths, or charging booths, and finance their childrens' education. (Women are seen as better clients for credit because they're less likely to spend the money on drinking and gambling.)
Look at the tech sectors in Europe and India and Asia--they don't have all these hang-ups and prejudices and misconceptions about how women's brains 'work differently' or what the biological differences might be or all that pseudo-scientific bull-crap. They just do the work.
You got some citations? Because in most of the countries you are talking about the poor who will do anything to survive aren't getting university degrees and sexist discrimination exists in abundance.
For example in many Islamic countries like Iran women do make up a significant portion of engineering graduates (sometimes even a majority) but few end up working as engineers due to sexism and cultural expectations.
I did some Googling and what I found didn't really support your argument.
>Every day we're bombarded with stories and images from the developing world of men, women and children trying to make a living.
I bet you are. I've actually lived much of my life in countries you would consider 'poor'. There is plenty of prejudice to go around.
>Look at the tech sectors in Europe and India and Asia--they don't have all these hang-ups and prejudices and misconceptions about how women's brains 'work differently' or what the biological differences might be or all that pseudo-scientific bull-crap.
Sounds like you have a lot of the world left to see.
> I wouldn't call being a teacher more prestigious than being an engineer, nor a social worker
I would. There's a lot of respect for people that do these things, because they are seen as somewhat selfless (partly because the monetary compensation is so low, partly because the jobs are so essential). Aid workers share in this as well. Prestige is about respect, and there are paths to respect that don't include a lot of money or power.
Speaking as a Canadian, I'd say that teachers are almost universally reviled here. Students hate them because they're the human agents of the school system; and parents hate them because they 'obviously' don't pay enough attention to and try to understand their 'special snowflake' kids, which is why the kid got a C- instead of the A+ they deserve.
I can't see things being very different in the States.
If you read the npr article that lambda referred to (http://www.npr.org/blogs/money/2013/09/11/220748057/why-wome...), it still feels like women choose fields that are cooler and higher prestige as opposed to being higher salary and lower prestige. lambda just refers to this as "rewarding" vs "mercenary"
I'm also going further disagree with lambda. For society at large, I feel that teachers and social workers do have higher prestige than engineers. Of course I realize that all of my opinions are just assumptions without actual data backing it up. However I do know this: the gender discrimination in both the military and finance are either just as bad or much worse, yet more women flock to both as opposed to our industry.
Sorry--you probably won't see this now (much like I didn't notice for a bit!), but you took the time to reply, so I figured I should, as well. I was (a bit tartly) hoping to get you to unpack why, in a very deep sense, you can't help but feel that way.
Does this have to do with how you perceive men and women? Does it have to do with how you perceive these various vocations? Is this feeling rooted in personal experience(s) and memories? Can you locate those in space and time?
It's important to challenge the ways we can't help but feel, because those are stumbling blocks when it comes to understanding what motivates other people--especially people who aren't like us. Our personal experience is always a fairly small slice of human life, and I'm concerned that you're projecting things you "can't help but feel" onto two of the largest populations.
But still, even though it cuts against some of your assertions about what is and isn't prestigious--it's a poll. It's messy. Hidden within its aggregations are the differences between what parents (of both genders) think would be prestigious for their boys, and for their girls. It hides differences between what is seen as prestigious in different ethnic, religious and regional communities. The way you "can't help but feel", whether about the people picking these occupations or the occupations themselves, is located in the messy middle of your own experiences.
There are communities where the most prestigious thing a woman can do is be a stay-at-home mother. There are communities where any occupation that doesn't pay at least six figures is an embarrassment. There are communities where going into finance is like selling your soul. There are communities where you aren't a real man unless you get dirty for a living. There are communities where academics are exalted regardless of pay, and communities where they're disdained for class, religious and political reasons.
This is all to say: The NPR article doesn't feel that way at all to me. But the way I read it doesn't mean your perceptions of the relative prestige of occupations are "wrong". They're probably quite right, given your experiences. Be open to the likelihood that your experiences don't generalize to others. Be open to the likelihood that the decisions other people make are better understood through careful consideration of their experiences than your own.
> Does this have to do with how you perceive men and women?
In the past compared to boys, girls simply aren't exposed enough to anything technical for them to discover it before their minds can get potentially tainted by popular perception compared to other fields. Is this changing? Yes. I feel that this will be much less of a problem for our children given the advent of toys like Goldiblox and even Lego sets aimed for girls. However I feel that this doesn't change the present situation for adults.
> Does it have to do with how you perceive these various vocations?
Yes because I've lived outside of places like Silicon Valley, in metros with a more conventional and old mindset.
> Is this feeling rooted in personal experience(s) and memories?
Yes outside of Silicon Valley it is strongly encouraged that engineers transition to management. It just isn't as respected outside of tech hubs and it's pretty recent. Is this changing for the better? It depends on the metro and the rate of change in perception varies.
> Be open to the likelihood that your experiences don't generalize to others.
I am definitely open to my generalizations being incorrect in many different places and times. I'm just stating what I feel is the general mass trend.
> I posted this elsewhere in the thread--I don't know if you saw it, but the Harris poll actually released some numbers not too long ago on the notion of prestige in various occupations
Looking that this poll and several other similar studies over the decades, my hypothesis has been proven wrong. Thanks for posting quantitative data. Yeah polls are subject to a lot of errors. Still, they're better than guesses based on personal experience. Logically I'm thinking that I've been proven wrong. However what's annoying though is that even in light of data, I still feel that I'm 'correct'. My gut still tells me that engineering is still seen by the masses as low prestige (outside of tech hubs like Silicon Valley). If I were to rationalize it, I would say that popular media is the main driving force behind my opinion. It's hard to ignore annoying shows like The Big Bang Theory. Ugh, I really hate that show. Another reason is that I feel the polls are measuring prestige incorrectly. imo A political office is very prestigious, yet in these polls they score so low. Why? Because the way the researchers measure prestige includes perception of ethics and generalized likability.
You can't compare being a teacher with a career in "law, medicine, politics, or finance" or a programmer. The latter all require very high intellectual aptitude, either logical/mathematical (programming, finance), memory (medicine, law) or social intelligence (finance, politics). In contrast, mostly everybody can be a teacher (and according to comment [1], teachers usually come from the bottom of their class).
Perhaps 20 years ago it was the case that anyone could get job as a teacher. That's very difficult from succeeding as a teacher, and it's also not true today.
Like anyone can be a lawyers or a programmer. There are good and bad ones, and a good teacher will require a lot of skills and 'logical' aptitude as well as empathy. AFAIK, you can't take a 4 week bootcamp and teach high-school math, but you can get a job at a startup after a rails bootcamp.
Can we stop with the 'we are so special/intelligent' arrogance?
The difference is that you only see you're bad at it when you're already a teacher, teaching a class. If you suck at programming, you see it in the introductory course of first semester of college.
Maybe not smart, but you have to have the ability to do a certain kind of abstract thinking. Like translating concepts into sequences of very precise steps (i.e. algorithms).
Right, and the Rust equivalent would be to define a newtype that wraps your floating point type and defines the ordering semantics you want; in Ruby, you have changed the behavior for everything that uses Floats (including other libraries that may depend on this behavior), while in Rust you can use your newtype, other libraries can use standard floating point behavior, and you won't have any confusion about who wants which semantics.
and the Rust equivalent would be to define a newtype
Which you can do in Ruby as well, as I pointed out just two comments below the one you're replying to.
The real advantage of Rust here was imho best explained by sanderjd; Rust can perform this check at compile time whereas in Ruby it's a runtime exception.
I'm curious why you characterize it as a "punishment"? Do you actually think that is why anyone designed the system this way, as some kind of aversion therapy just to get you to avoid using floating point numbers?
All Rust is doing here is implementing IEEE 754 floating point semantics as specified, and implemented in lower level hardware. Part of the IEEE 754 specification that you need to deal with if you want to use floating point numbers is NaN, which represents not an actual value but the absence of a value, an indication that your computation did something that could not be represented. Because NaN is one of the possible values of a floating point number, a typesafe interface for comparing floating point numbers must, by definition, be a partial function; and as a partial function, it cannot be relied upon for implementing sort.
The Rust way of doing this does not punish you, it just ensures that you actually think about, and deal with, edge cases like this. While that can seem cumbersome in a small, one liner example like the above, or can seem restrictive when you're writing a simple personal project and you know that you will never encounter a NaN and so you just want to sort the values without thinking about that, it can be quite valuable when programming in the large; when you are working on a program larger and more complex for any one person to know and reason about the whole thing, type safety allows you to encode certain constraints in the type system that ensure that you don't make mistakes.
For instance, if you write code that depends on sorting a list of floating point values in Python, like in your example, and write all of your unit tests and design using non-NaN floating point values, then use a third party library that winds up producing a NaN value, you are likely to be quite surprised by the outcome:
Now, deep in the middle of production code, that result might not be so apparent. Most of the values that you care about are ordered correctly; but eventually you'll hit the fact that the 1 is sorted before the 0, so you'll have some strange, hard to reproduce bug, that depends on the precise ordering of the original array.
What Rust is doing is not punishing you, but instead just making you make that decision about what to do about such a case up-front, before you accrue that technical debt that comes to bite you later on.
There are several possible ways you could deal with it; one is the one you mentioned, where you just define some way of comparing NaN so that you now have a total order. Another would be to panic any time you try to do an undefined operation like comparison on a NaN. Or you could work with a type that is restricted to non-NaN values, and deal with the issue only at the boundary of components which convert between arbitrary floating point values and your restricted subset (and any operations that may produce NaN values).
In order to not have to write those cumbersome sort expressions by hand every time, if you need to work with floating point numbers with one of the non-standard semantics described above, you could define any of the above behaviors by creating a newtype the wraps floats but provides the semantics you want. Since they are static types, there will be no overhead on the values, they will just be represented as floats; you may have some overhead on your checked operations that wrap the underlying float operations, but that the price you pay for going with semantics which are not the standardized IEEE 754 semantics as implemented by the hardware. In a larger project, if you need such a type, it's not all that much work to just define that type once with the semantics that you want, and then just use that everywhere rather than using one of the native floating point types.
So, what Rust is providing is a type-safe, low-overhead implementation of IEEE 754 floats, without providing certain conveniences that would make your life easier when dealing with a subset of them but cause problems when working on the full range of values.
Can it be convenient to accrue technical debt in order to get things done quickly? Sure. Shell scripts are a classic example; almost every non-trivial shell script will have some kind of quoting bug, delimiter bug, confusion between arguments and flags if an argument value ever contains a "-", or the like. But because they are familiar and allow people to get things done quickly, they can be really useful for little one-off hacks, especially when you're working with data that you know is simple enough not to hit one of those edge cases, like filenames where you know that none of them contain spaces.
However, you need to be really careful about that sort of thing. That kind of quick and loose reasoning can quickly come to bite you if it gets deployed in production in an uncontrolled or even hostile environment. All of as sudden, the things you thought could never happen will happen. I've seen a seemingly innocuous shell script for cleaning up a few particular types of files turn into an "rm -rf *" due to a bug in handling of spaces in filenames (and yes, an actual customer lost actual data due to this bug).
So, is Rust appropriate for that kind of fast-and-loose exploratory programming that the shell or dynamic languages like Python allow you to do? No. If I were working with known inputs, interactively, where I could easily tell that I didn't have NaNs and could check the outputs to make sure they were sane, I would choose Python and numpy, or Julia, or something of the sort that was more appropriate for rapid and loose prototyping.
But for software that will be deployed in the wild, where I need to write modules that will work with values provided by other modules that I don't control, or the like, making you think about this kind of thing up-front can help you avoid having weird, obscure, hard to debug problems, or even security vulnerabilities, down the line.
No safety has been added, no technical debt has been avoided. It's not any less "quick and loose".
The need to sort arrays of floats doesn't disappear simply because the Rust designers will it to. The code will still exist, but it will be longer and less maintainable. This is what I mean by punishment.
If anything, Rust has given you a false sense of security. The modules and other code you work with will still be handling NaNs incorrectly.
My preference, all considered would be a .sort() that pushes the NaNs to the front or back (but is slightly slower), and a .sort_unsafe() that assumes no NaNs but is faster.
I'm still reeling from how cynical and dismissive this comment is. The Rust developers don't like IEEE 754 any more than you do, but it doesn't change the fact that IEEE 754 is what hardware implements. I encourage you to take your complaints up with hardware vendors and the IEEE, as well as with with the popular programming culture of blindly pasting SO answers into your programs in frantic attempts to get them to compile at any cost. As for me, I very much appreciate that Rust is conscientious enough to throw up a red flag and force me to realize that this seemingly-simple task is actually quite complex, rather than implicitly imposing a leaky abstraction.
Well, hopefully first answer will be stack overflow which will address this topic :P Rust community has been hard at work, answering a lot of Rust question. I don't think I've seen many unanswered so far.
Well, when Bob found sort_by and a weird partial_cmp he should have paused there and look at docs if he understood nothing. In case of Python he is rightly to blame Python for silently doing stuff for him that he doesn't like.
It's like a speed bump. If you go fast over a speed-bump, ignoring it, you suffer the consequences. It's different than a dark unlit road that just has a sign THIS WAY.
> Or you could work with a type that is restricted to non-NaN values, and deal with the issue only at the boundary of components which convert between arbitrary floating point values and your restricted subset (and any operations that may produce NaN values).
How often do NaN's appear in practice? I think it makes perfect sense to handle IEEE 754 floats like this, but maybe rust should follow your suggestion here and provide a new totally-ordered float. Maybe `f64` should _be_ this totally-ordered float and IEEE 754 could be imported if you need to use that one?
That would likely make operations on the default float slower than they need to be. After all, the CPU is probably implementing IEE 754: How do you handle it when a NaN bubbles up from below?
You are cool. I'd like to read your twitter or blog (link please). I don't see here any personal messages to ask it another way. I just respect professionals with knowledge.
Sunlight. We can synthesize vitamin D ourselves when exposed to sunlight.
One of the explanations I've seen for why Europeans are white is to enhance this effect, because Europe gets comparatively less sunlight than other regions in which civilization initially spread, but was warm enough due to the gulf stream to support agriculture, which produces a diet lower in vitamin D. So between the comparatively lower sunlight and agriculture, Europeans needed to evolve to be able to generate more vitamin D from sunlight, which losing pigmentation helps with.
Absorbing photons into melanin pigment and dispersing their energy as vibrational motion (heat) doesn't help synthesize vitamin D. For the synthesis you need the photons to hit an intermediate molecule in the pathway and boost an electron into an excited state. If there's a bunch of melanin absorbing photons before they get to the synthesis pathway, the synthesis will be inhibited.
Less sunlight being absorbed by eumelanin in the skin means more sunlight left to be converted to vitamin D. Window glass also blocks most of the UVB part of the sunlight that would be converted to vitamin D.
I think that it's a little bit of a problem with a lot of the modern "social web" mindset; it all implies that you should feel comfortable doing everything in public, with the whole world watching you.
The problem is, there are people for whom this really doesn't work well. Some might just personally feel uncomfortable about it. Some might be concerned about future career prospects. Some might be women, who are worried about online harassment. Some might be people with stalkers, who are trying to avoid any kind of traceable online public trail.
This whole "share all the things" mentality leads to somewhat creepy exposure of everyone's private lives to governments, corporations, the general public (which can act as a mob on occasion), and also specific private individuals who you might be trying to avoid exposing things to.
I wouldn't say that HN "is" a bunch of MRA losers; HN is a big place, and there are a lot of different types of people on it.
But there are a bunch of MRA losers on HN. How many, it's hard to tell; maybe a few that are very vocal, maybe a few with many sockpuppets, maybe a lot. If you ever get involved in a thread about any issue about women in technology, programs for encouraging women in technology, or the like, you will see them come out of the woodwork (and such threads will frequently drop off the front page as the long comment threads trigger HN's algorithm that try to discourage flamewar topics).
"MRA is short for Men's Rights Activist. MRAs argue that, as human beings, men should have human rights, due process in legal matters, and should not be subject to "reverse discrimination" in favor of other groups.
MRAs typically point to men's lower life expectancy in almost every country, higher rates of incarceration, more severe penalties for similar offenses, lower rates of health care spending and health research spending on men, higher suicide rates, higher rates of being subject to violence and murder including by women and when they are children, higher rates of genital mutilation, liability to conscription, higher rates of death at work, various disadvantages in divorce and child support, and higher school and college dropout rates, as reasons why men's rights should be on the agenda."
A lot of people feel that since men are privileged in so many areas, no effort should be expended on men's issues until every women's problem is entirely resolved. Due to that scapegoating Men's Rights Activists as people who hate women is popular.
So how does any of that make you a loser? What's going on in this thread? As far as I can tell it's nothing more than a similar type of bullying the article is itself is talking about, which I didn't ever expect to see on HN, let alone tolerated.
At what point can you no longer express controversial opinions without being called a loser?
It doesn't make MRA losers. If it did there would be no reason to tack the word loser on. Being an mean, agressive alcoholic bum implies being a loser so you don't often see loser tacked on.
On the Internet, someone is already calling you a loser, possibly without your knowledge. It's best to worry more about the folks who have greater power to destroy your social standing than just simple name-calling.
And to provide a sentinel value for the previous search space, I'll just say it. You, and everyone else who may be wondering if someone on the network is calling them a loser, are all losers.
Now that's taken care of, and you can go about your business, expressing controversial opinions without worrying about incurring greater harm to yourself than has already occurred.
The reason you'll get banned for such behavior, and the whole reason why such behavior is against the rules, is because personal attacks are counterproductive to logical discussions. When HN degenerates into a group of people who go around calling other groups of people losers, that does not bode well.
It was, I admit, somewhat of an obscure joke. I realized, after my first sentence, that I couldn't be certain that it was true. So I added a sentinel value.
>As far as I can tell it's nothing more than a similar type of bullying
It absolutely is. "MRA" is a short cut to dismiss an entire spectrum of arguments and perspectives. Just as farcical, but on the opposite side, are people who declare anyone who has a problem with something like, say, "GamerGate", a "SJW".
These are shorthand for idiots. It lets you pretend that you're in a tribe and everything is black and white.
I am an advocate for men's rights for many of the reasons you cite, but I also acknowledge that there really are people who adopt the MRA label who are bitterly misogynist nutjobs who have no interest in a more just and equal society, but are rather the flip-side of those misandric feminists who believe--amongst other things--that "rape is nothing less than a conscious conspiracy by all men against all women" (likely not an exact quote as it's from memory, but Brownmiller says something with the same meaning.)
The problem is that misogynist MRAs disrupt the possibility of positive change the same way misandric feminists like Brownmiller and McKinnon do. Because they share a label with sane people, they allow the enemies of sanity to mount a trivially plausible ad hominem against any proposal to genuinely address the real injustices that men and women face due to the simple fact of being a man or a woman.
There are lots of good reasons to talk about issues affecting men, but sadly the bad parts of the MRM far outweigh the good at this point. I'd say it's 85% bashing feminism, complaining about women's sexual power (e.g. The Friendzone), denying and minimizing rape as a social problem, etc. and only 15% talking about fathers' custody rights and boys' education issues.
Yes, this could be more accurately described as "investing his fortune", or if you want to focus more on the risk (as game development is a risky business), "bet his fortune."
Loved Braid, quite interested in trying out The Witness; hope it doesn't take too long to come to a platform I can play it on, as I have neither a Windows machine, nor any consoles, nor an iOS device.
I think part of the reason they consider he is "betting" or "risking" his fortune, is because it probably has a lot more risks than a "simple investment". i.e. he's not taking his money and putting it in a Fidelity investment account, he's spending money to create a game that might very well not sell more than a few copies and not make the money back.
I guess people see him as "winning the lottery" with Braid, so now spending that "lottery money" is seen as a foolish move. However I think that spending/investing your hard-earned money in something you enjoy (developing games) is the best investment one can do, even if you do lose all your money.
Also, note that some of these "most downvoted questions" are also among the most upvoted as well, having very large positive scores, like https://stackoverflow.com/questions/1642028/what-is-the-name.... Once a question becomes famous enough, there are likely to be a number of contrarians who don't like it and downvote it, and eventually that can add up.
And then if you look in the comments of some of them, that seems to be not too bad but which have more downvotes than you'd expect, they got a downvote brigade because they complained about a few downvotes on meta. Pretty lame that people do that, but it happens.