Depends on whom you ask. There are people who use it exactly because when "things break at random" they absolutely can understand the reasons and actually fix it in contrast to some other OSes (or Linux from more recent years).
Depends on whom you ask. There are people who use it exactly because when "things break at random" they absolutely can understand the reasons and actually fix it in contrast to some other OSes (or Linux from more recent years).
In this particular case I assume the operator will be thrown under the bus, which is also unfair.
Tough luck, 5 million dollars to the family?
So if git is the tool you use to get your job done - don't hesitate to spend a day or 2 on reading how it works and how you're supposed to use it.
The stereotypical case of rape would involve two people who know each other, may have had a prior intimate relationship, and then did something behind closed doors with no witnesses. One person will claim it was consensual sex or, failing that, that they had a reasonable yet mistaken belief that it was consensual sex. The other person will claim it was non-consensual sex, and that the first person did not have a reasonable believe that consent was present.
What are the police meant to do with that? Both parties agree that they were together, in the room, behind closed doors, and had sex; the disagreement hinges over extremely specific details about what was said and how it was interpreted. Classic police tools (checking alibis, interviewing witnesses, pulling security camera footage to track someone's movements, speculating about motives, following money, running DNA tests, checking forensics) are all totally useless here.
It's possible the justice system is failing to bring charges in cases where there is a strong chance of proving a crime occurred beyond reasonable doubt, but the nature of rape makes most cases extremely hard to prove, as the linked example makes clear. Here:
"The [woman's] colleagues took her out for drinks [...] after a night of drinking, she crashed with a male intern and his friend who lived in a group house nearby. She fell asleep in the basement [...] but during the night [...] the male intern [...] “forcibly penetrated her while she was sleeping”."
That's her story and I have no reason to think it's false. But here's the thing: All the guy has to do is say is something like "oh, I went down to check on her, she was awake, we chatted a bit, she seemed sober, we flirted, I propositioned her, she said sure, we had sex, I gave her a kiss, and left her to sleep" (or some variation of that; basically anything that expresses a reason why a reasonable person in his shoes would have believed she was consenting). And here's the thing: His story doesn't need to be true; it just need to be possibly true, because a conviction would require proving it was untrue beyond reasonable doubt. As long as the male intern says something that implies he had a reasonable belief in consent, and there's no third party witnesses willing to testify to undermine his claims, the justice system is powerless. And rightly so. (If he was dumb enough to claim they hadn't had sex at all, and the rape kit proved otherwise, then he'd be in trouble, of course. The rape cases that the justice system can deal with are the ones that hinge on whether or not someone was in the room, or whether or not intercourse took place. Ie, the rare easy ones.)
> Do people believe that the standard of evidence for Police is too high but isn't politically possible to change?
Not at all. It's good that the justice system works by requiring crimes to be proven to a jury of one's peers beyond reasonable doubt, and that shouldn't change.
> If someone files a police complain but that complaint is dismissed for lack of evidence, how exactly should Microsoft evaluate that claim?
Microsoft should evaluate the claim at face value. What the police do is entirely separate. If one intern is convicted (and only then) Microsoft can decide if they want to hire a rapist. Until then, they can look at the fact that two of their interns have had an extremely unpleasant encounter. Deciding to hire both, and then assigning them to the same team is clearly the wrong solution, whatever did (or didn't) happen that night.
Couldn't Microsoft also get into trouble by hiring just one of them (the other one could have a good case for being treated unfairly)? And what if they don't have 2 separate teams which need new members? Should they create a new team just to make sure they don't heart anybody's feelings?
Now, let’s look at the statistics. Rape is much more common than false accusations of rape. Now, you run a simulation using these statistics. What happens? The rule of believing Alice results in vastly more cases where you make the right decision than the rule where you believe Bob. And it results in vastly less social harm overall.
So what’s fair? I’d assume that you’d say it’s to believe Bob, since you have no “hard evidence” to the contrary. (To nitpick: a sworn statement by a witness, Alice, is evidence admissible in court.) But that means that 10-20 women are forced to leave their jobs or work with their rapists for every one man who is spared from wrongly being fired due to a false accusation. From the point of view of minimizing social harm, you’ve failed.
Of course, in reality, you’re usually going to have some other evidence to go on. Bob might say, “Alice is lying I was at the bar with my friends when the alleged rape happened.” If so then you should believe Bob, of course. The idea of shifting the burden of proof might not work in a criminal case, but for the reasons explained above, the considerations in a work place scenario are very different: false negatives are just as bad as false positives.
You're throwing away a datapoint - "the police decided not to press charges or Bob was found not-guilty in court".
Not a lawyer, but isn't is taken for granted that lawyers (along with everybody else) are lying in courts and that it's the jurors and judge's job to find out who is lying?
> Over the years, I’ve used Perl a lot (that one doesn’t care if it’s int or string… no, correction, in Perl everything is a string, ints just don’t exist. Well, kind of). It’s probably the language designed for throw away coding. I’ve done some Python too (that’s like Perl, but with proper objects in it, and everything is a dictionary there).
The author has almost no real programming experience with Python. Perl experience seems to overlap with sysadmin-related work at least partially, where it's usually used as better Bash. All their repositories in GitHub are Rust. So almost all of "real" programming they did used Rust.
Why would anyone who know Rust way better than any other language prefer to do their prototypes using anything else?