And now that we've been paying AT&T for 4.5 years of unlimited service, they are taking it away because our devices made it easier to consume the data. [...] Now AT&T is calling foul? AT&T should either stop grandfathering the plan forward or leave us alone.

Amen. Are so many people grandfathered into the unlimited plans that they feel the need to throttle us? Really? Piss off.

That's a huge topic

Indeed.

...that both PRC (mainland China) and ROC (Taiwan) agree there is only one "China", but disagree over which government is legitimate.

Which is a great piece of political mental masturbation but of little use in reality, where there are separate governments and separate courts and separate financial institutions at play.

(Taiwan+China are technically the same country)

In what way are they the same country?

One undergraduate spending 12 weeks porting Darwin (!) to a new CPU architecture as part of their senior internship should not be used to infer anything about what Apple will be doing moving forward. Have people lost their minds? This is the biggest non-story I've ever read. He could just as easily been doing this with *BSD or Linux or OpenVMS or whatever. Honestly.

http://www.cs.dartmouth.edu/reports/TR2011-705.pdf

This is unfortunately just the way it is: some places do the Right Thing (for various meanings of Right Thing) and others do not. Now you'll know to ask about this kind of thing when you interview. :-)

... there is a critical mass on FB that G+ is going to have a hard time beating. Many of the people I interact with on FB are family members (who won't switch because they have no need to: it's a wonder they're on FB at all) and old friends from High School and College, many of whom won't switch because they see no point in doing so (and, as I said, probably have family links that they don't want to loose.) Unfortunately even though (if?) G+ is better, it's unlikely that people will will switch en masse. It is highly unlikely that G+ will do to FB what FB did to MySpace.

It can be disabled with a single shot. It doesn't even need to be a particularly well placed shot.

I was working on a project at Spyglass in the late '90s that did this... it isn't a new idea. It just got pushed to the background when devices started getting more powerful and bandwidth increased.

I'm not sure I understand the point of this extension: compile time type safety for internal (i.e., compiled) queries against a full-text database. Seems like a nice POC that has really no use in real life. The "rogue-like" moniker escapes me completely: is this some reference to database technology I'm not aware of? I just found it confusing.