This is a fascinating problem. I can see the feature being incredibly valuable, yet awful as it's currently implemented. Is there an approach to doing this safely?
Yes. Won't someone think of the small developers?
-- A small developer.
And a bad month for Samsung.
Perhaps they are. It is remarkably difficult to secure a large code base.
Though I would hope that NFC is new enough that it would be coded securely right from the start.
Use Sun's site to check:
I doubt it's still installed after an upgrade, though.
Given that the virus no longer exists outside of labs, vaccinating everyone for it at a cost of 300-600 lives is very significant.
I know I don't. Are you sure Google doesn't?
If everyone in the US received the smallpox vaccine, 300-600 people would die. That's not insignificant.
WebP lossy may not catch on, but it isn't pointless. Compared to JPEG, in return for a muddier image (to my eyes, at least) you get alpha support. As Google is one of the biggest distributors of images on the Internet, I think the real purpose is to pay less for licensing JPEG.
WebP lossless seems much less useful to me. Unless there's licensing issues I'm not aware of, it seems pretty pointless.
Because the current smallpox vaccine can kill. Not many, sure, but if you try to apply it to an entire population? Some people are going to die.
Only because it's already old news in Internet time.
"Quick! Let's turn the conversation to jail breaking!"
You think the Mac App Store is simpler, licensing-wise?
Not at all.
Microsoft is pushing Metro as their new UI, and (possibly, it sounds like Microsoft hasn't even decided) their only ARM SDK. Of course they have an Office port in the works. Otherwise, Office would be unsellable.
Coincidentally, at my company we decided on a (gradual) move from XML to JSON yesterday. (We've discussed it a number of times, but this time we finally made the choice.)