That was really the weakest point of that story and really completely unnecessary. Considering that Doctor Who established that a Weeping Angel is a -stone statue- that can't move at all if anybody is looking at it, it makes no sense at all. First, the Statue of Liberty is not stone, and second, is there actually any point in time where -nobody- at all is looking at it?

That's quite a generality. I've been to my daughter's high school and the teachers there don't appear to be lazy in the least, AND they seem to be leveraging technology in sensible ways. For example, the way my daughter can log in to a school web site and see every day's lessons and homework assignments.

"We have only bits and pieces of information but what we know for certain is that at some point in the early twenty-first century all of mankind was united in celebration. We marveled at our own magnificence as we gave birth to AI.”

I took a look at TFA and followed up by reading the description of LibGeoDecomp:

Gee, that seems like an extremely limited problem space, and doesn't measure up at all to the title of this Slashdot submission. It might really be a useful tool, but when I clicked to this article I expected to read about something much more general purpose, in terms of 'bringing Legacy Fortran to Supercomputers'.

By the way, regarding the use of the word 'codes': I don't think English is the first language of this developer. Cut some slack.

Well I guess Elon Musk hasn't gotten the memo yet, that there's no way he can do heavy lift, because he certainly seems hell-bent on trying. Now do I know whether or not designs like the Falcon 9 Heavy or Falcon X Heavy can ever get off the drawing board? No I don't. But I'd love to see Musk try, instead of bowing to 'prevailing wisdom' that only the government can do this.

... But we do know it was us that scorched the sky. At the time, they were dependent on solar power. It was believed they would be unable to survive without an energy source as abundant as the sun.

So much for that bright idea.

Well patch.com is trying. I can't say they're yet but at least you get some local news out of their sites.

In my area I think retailers realize there are too many consumers who don't get a newspaper, so a bundle of advertising is bulk-mailed every Thursday for free. It provides flyers for most of the area supermarkets, a few hardware and department store flyers, and occasionally some coupons. And a lot of it is still printed on newsprint. We also get the advertising envelope bundles like Valpak and the like.

By the way, I don't think newspapers are even a particularly cheap source of paper, considering how thin many local newspapers have become. You can get a better deal buying a ream of paper at an office supply store, but I admit it won't burn as well or protect your packages like crumpled newsprint.

This is the first thing I ran into as a newcomer to Node. Not just packages but programming techniques. You're trying to learn how to do something trivial for the first time, so you hit Google and then drop into Stack Overflow and find plenty of questions and answers about your very problem. Then you try to use the solution and it falls apart. That's when you look back through the comments and you discover, "Oh yeah, I wrote that answer / released that package for Node 0.4.x: it really doesn't work anymore, sorry."

This isn't really an indictment of node, because I see this now wherever I look into the Web world (coming from the C/C++ world). So much immaturity (in the literal sense). Everything: HTML, CSS, Standards, Real-world browser support for said standards, VMs, best practices for JavaScript, tools like Dojo, Node, etc. all in flux. Documents that describe the "deprecated" old way, the new "approved" way, and the "better" way that doesn't work yet but will when the next revision is coming out (date TBD). A little more stability would go a long way.

Well the people who created Space Quest don't own the IP to Roger Wilco now, but they had this Kickstarter last year which achieved its funding:

http://www.kickstarter.com/projects/spaceventure/two-guys-spaceventure-by-the-creators-of-space-que

Actually the court decision still allows one state to refuse to recognize the same-sex marriages performed in another state. The decision only ruled against the portion of the law allowing the Federal Government to not grant rights and benefits to same-sex partners legally married in their home state.

So, basically the overall effect of the decision is: Legality of same-sex marriage is still each state's right to decide, but the Federal Government must abide by the rules of each state which ever way it goes.

http://en.wikipedia.org/wiki/Defense_of_Marriage_Act

The Supreme Court ruled in 1967 that state laws against mixed-race marriage are unconstitutional. That decision immediately nullified all such laws (even if the states didn't take them off the books, as in Alabama which didn't repeal the ban until 2001, it doesn't matter).

Someone might say, 'well I don't see anything in the Constitution that guarantees the right to mixed-race marriage', but that opinion, or even that of Congress or the President, is not what matters. The role of the Supreme Court was established in the early 1800's as the final arbiter of what the words in the Constitution actually mean.

http://en.wikipedia.org/wiki/Anti-miscegenation_laws_in_the_United_States

http://en.wikipedia.org/wiki/Supreme_Court_of_the_United_States

http://en.wikipedia.org/wiki/Judicial_review_in_the_United_States

Some of this discussion seems to be assuming that autonomous cars will -have- to talk to one another? Why? The Google prototype car doesn't talk to the ordinary human-operated cars on the road. It just deals with them with its sensors. As far as I can tell the Google car is designed to safely take itself wherever a human driver could take it.

So what are the 'network' and 'compatibility' issues?

You forgot Hyperspace. I'm sure the ISS astronauts want that one too.

You're thinking of Surface RT. Surface PRO requires an x86 compatible processor, namely an Intel Core i5: http://www.microsoft.com/Surface/en-US/surface-with-windows-8-pro/specifications