They should have applied for .lulz

Fair enough.

At work, I get the choice of the Dell "Power User" Business Lattitude. - Or?

A MacBookPro.

I need to run ESXi virtualised on top of Workstation or Fusion. Dell killed me, trying to get this to work - 4 cores and all...

So Apple's limited choice in models, and non-responsiveness to IT requests for support features plays to the interest of the user.

Sure, I'm OK with that.

1. S/he is going to be acting more out of curiousity than sexual interest (kids that age have sexual interest, but nowhere near as much as s/he will when their 13). When young kids see something sexual, the tendency is to get bored with it really quickly.
2. By taking the mystery away, I'm reducing the chance that s/he'll experiment unsafely when their 12 or 13.
3. It can be a "teachable moment" where I can explain the difference between the fantasy of banging Megan Fox and the reality of an actual relationship with Megan next door.
4. The average child in the world sees a boob within the first hour of their existence. Children generally will see people of the opposite sex nude at least a few times before entering first grade. And they will likely know the basics of what body part goes where by the time they're about 10.
5. Historically, most kids were conceived in 1-room homes that the parents shared with the new kid's elder siblings. Plus most kids were raised on farms, so they would have seen animals going at it quite a few times as well.
6. Sex is hereditary. If your parents never had it, chances are you won't either. (In other words, every single generation has figured it out, there's no reason to think the next one won't.)

About the only areas of most porn that are really going to cause problems long-term are that porn doesn't typically demonstrate the use of birth control.

https://en.wikipedia.org/wiki/Goatse.cx

Wikipedia entry contains 42 references cited.

And now, they've "Sub-standardized".

Thatcherite!

That's a vendor doing their own integration on PoketPC.

Microsoft didn't offer RIL for radio stack integration until 2002:
http://en.wikipedia.org/wiki/Windows_Mobile

All of this is pedantic. MS phones came with A STYLUS, until 2006! They made shit phone software for 4 years, with no market success and had to be SCHOOLED by Apple.

The Zune 2nd Gen would have been a beautiful "catch-up" point for MS. They could have used their finally elegant iPod knock-off to build the iPhone knock-off. But they screwed that pooch in the kennel. The Zune IP was ditched and users abandoned, in the mindless pursuit to keep "Windows" relevant, and build anew for the tablet "strategy" they'd also gotten TOTALLY WRONG since 2004.

After spending over 12 Billion on R&D labs between 1999-2010, you think they'd come up with something other than wannabe OS's, devices and me-too cloud services.

The separation of church and state is thoroughly implied by those phrases:
1. "respecting an establishment of religion" means that no religious viewpoint or organization can claim a privileged place in government. In other words, church stays out of state.
2. "prohibiting the free exercise thereof" means that government can't decide what religious viewpoints are acceptable. In other words, state stays out of church.

Many American Christians want their religious viewpoints to be established at least semi-officially, and the more extreme want to ban other religions (basically things that aren't Christianity or Judaism) from the United States.

Note that this is not the same concern as voting as one's religion dictates: If a Catholic wants to vote against those who supported government paying for contraception, no legal problem with that. But that's different from saying "Everyone's going to stand respectfully while Father Michaels recites the Lord's Prayer" at a public school graduation.

Agree.

As you increase the general-purpose utility of any piece of technology, you open corresponding opportunity for abuse or exploitation.

Security comes through ongoing practice. This includes implementation specifics, ongoing management operations and individual initiative/decision capacity of users.

To believe there is a technology solution that - correctly implemented at the correct point of design and lifecycle - would automatically solve the security "problem"? This is a naive point of view, which ignores the wealth of research and understanding acquired in the field of systems security, over the past 20 years.

This is not to argue that nothing can be done. But assuming that security can be "solved" with just the right design and development is cruelly untrue.

And I have yet to see this security-conscientious, aware development community to which the article makes reference.

Decade? How about 4 years. CE was around, but not for phones. When they stuck these together, as Windows Mobile, the integration of the radio stack and network controls were at LANman / Win 3.1 levels of sophistication. Really. The phones were life safety hazards, where stalled applications could keep you from answering or starting calls.

Trust me. I had every one one of these turds, 2003-2010. Starting with the TMobile HTC Wallaby and Himalaya XDA, which opened the market - a couple of the unusable HPs and then the Palm 700w and back to the HTC Vogue. Finished off the pile of misery with the Samsung Omnia.