I hate to be the cynic, but this looks really contrived. And phrases like the one in the abstract "we learned that science can be cool" (paraphrased) are so old hat and trite. I hear my kid come back from school programmed to say the same thing. It seems that this work could give the children involved what actual scientific work is like. I am concerned that the real reason for this work to further the career of their attention getting teacher. [Just conjecture.]

Another missing option - Commodore BASIC. I love that it was a language and an operating system. Same for the HP 85 and many others...

So it's OK to talk about her "panties" now? Not very civil. And we women just call them underwear nowadays. The 1950s was oh...about 60 years ago.

I think they moved it to the Firehose so you have to put in a little effort if you want to tag a story (presumably to cut down on tags like cyberwarfareisbullshit)

What's the point of a single-use patch? I had a tetanus shot the other day, and needles are so thin now, I literally felt nothing.

Now, once the shot took the spot on my arm was sore for a few days, but the needle was absolutely painless.

This just seems like a less controlled and more expensive way to do the same thing.

Acoustic triggers are, by law, required on all offshore rigs in Norway and several other countries. Norway is, quite simply, the gold standard for sea drilling, and you have no idea what you are talking about.

I'm not sure if you're ignorant or just a troll.

In any case, SSL is responsible for securing all updates, OS or app. Break Google's SSL, you've compromised all of the features, and you're not going to bother installing a crippled Android app, because you have root on a full-fledged Linux handheld.

The line between OS version and app is entirely arbitrary, and Google is working to move more of the OS functionality into apps.

From a security standpoint, if Google has access to this, they have access to the OS anyway, installing/removing apps is not a big deal. They already have root on your device (and you don't.)

If your solution doesn't work in the latest Opera, Firefox, and Chrome, you're not developing for standards. You're developing for whatever browsers you're developing for.

If you are in a situation where you can dictate what browser your users use, you can do that, and I think it's fine to say that it can't be IE until Microsoft gets their act together. But the other three rendering engines - Presto/Webkit/Gecko - should be supported 100%.

It's not a solution in that it doesn't create a wide market where app developers can target at least a third of majority of mobile phone users. People want too much variety for Apple to grab that much of the market with only a handful of models.

Actually, I think Android strikes an excellent middle ground between the iPhone (native only, a handful of models) and Windows Mobile 7 (Silverlight only, a plethora of models.)

For most apps (even some games) the Java toolkit is more than adequate, and functions very well across devices with minimal tweaking. If you need performance, but still want your app to work on a variety of phones, you need to do more legwork.

Apple doesn't actually have a solution to this problem, they're just protected because they only make a handful of devices.

AOL was built on top of the Internet.

You can run C code with the NDK.

Of course, when people talk about Android fragmentation, they don't know it, but they're really talking about the NDK. If you stick to Java your program is fairly easy to keep working across versions. If you use the NDK, it's graphics programming in the late '90s again with a ton of different GPUs and odd CPU quirks to deal with.

The Pandora hardware is closed once you get to the level of individual chips, though it's not that big a deal for someone trying to build one.

With the nodes that insert a backdoor into the unix login program colored red.