I do most of the time when standing or walking, mostly because it's uncomfortable in the front pocket and difficult to get out. I have a Nexus 6, so it's a bigger phone, and no I don't wear skinny jeans. That being said, I take my phone out whenever I sit down. It's second nature at this point, I don't have to even think about it. So no worries about sitting on it and bending it.

The headline, I think, is the worst part; the choice of "doesn't" (vs. "can't") sets up the expectation that MS is refusing to hire qualified women. Perhaps that's true on some level, but it's certainly not the story...

Posted
by
Soulskillon Saturday July 18, 2015 @11:50AM
from the trying-a-different-pitch dept.

theodp writes: "It is not surprising that the U.S. women have been dominant in the sport [of soccer] in recent years. The explanation for that success lies in the talent pipeline," writes General Manager of Citizenship & Public Affairs Lori Forte Harnick on The Official Microsoft Blog. "Said another way, many girls in the U.S. have the opportunity to learn how to play soccer and, as a result, they benefit from the teamwork, skill development and fun involved. That's the kind of opportunity I would like to see develop for the technology sector, which presents a different, yet perhaps even more significant, set of opportunities for girls and young women. Unfortunately, the strength in the talent pipeline that we see in female soccer today is not the reality for technology. The U.S. is facing a shortage of Computer Science (CS) graduates. According to the Bureau of Labor Statistics, every year there are close to 140,000 jobs requiring a CS degree, but only 40,000 U.S. college graduates major in CS, which means that 100,000 positions go unfilled by domestic talent." Going with the soccer analogy, one thing FIFA realized that Microsoft didn't is that if you want girls to play your sport, you don't take away their ball!

Same with Comcast. I tried for a years actually, but some things were too slow. Ubuntu and Debian repos in particular were painfully slow, even on my VMs on linode, digital ocean, and prgmr. I ended up having the servers force IPv4 for them when their IPv6 servers went down for days. Speed and latency on IPv6 have gotten much worse over the last couple years in my experience.

Also, it appears Android doesn't play nice with IPv6. It basically silently drops the connection eventually (I'm guessing it stops listening for the RA broadcasts), and push notifications fail. Happens on Samsung devices and my Nexus 6. So it's reliable either push notifications and low latency site loading, or use IPv6. I finally bit the bullet and disabled IPv6 on the router and all my issues went away.

I mentioned the +/- zero thing in another comment elsewhere in this tree, actually! So we're all on board there.

It's not really that signless infinity is a contender for 'consensus' inasmuch as number systems which use signless infinity have utilities different from systems that have signed infinities, just like integer math continues to exist despite the 'improvements' of fractions and decimals.

Same reply: Python is not fully functional, and so list constructors like that cannot be counted upon to work elegantly in all situations. This is a completely normal thing common to basically every imperative language, and it's just something you have to accept—and write a special-purpose function for.

I think that just means you're a zealot of functional programming; your expectations are wrong. If the language isn't fully functional in nature, don't expect key patterns like map() to work elegantly. They're hacks at best and not really part of the core language design; this is excellent proof of that.

You're just validating your own arbitrary decision to use that integer set. IEEE 754 defines positive and negative infinity separately. (However, if you look at the other comments below this one, you'll see that I argued for exactly this, reassigning the largest negative value to NaN in a signed integer format—but only for select situations.)