One of the issues I have with online DRM being required is the fact that someday the console and ALL games ever made for the console would have stopped working, forever. I'm old enough now to have games in my collection that, if it had been originally released with online DRM, would no longer work today. At least now, users have a choice between the convenience of digital downloads or comfort in the fact that the physical disks they buy will still work years after the DRM for digital downloads is shut down. Without that choice, it's inevitable that a huge swath of cultural history is, at some point, going to be lost forever.
Sleepy Daddy Software
|Coffeehouse||WOA details start to emerge||16||Feb 20, 2012 at 6:43 PM|
I soooo wanted the roboball demo to work! Presenting the content in first-person narrative was a little distracting, though I liked that it told a continuous app use case/story. Would have preferred a straighter, less scripted presentation in second person narrative, as if you are pretending the audience is doing the work and you're just guiding them through the process.
@wkempf: In principle I agree with you. In practice however, it would be disastrous if IE came out with a completely incompatible specification, no matter what the reasoning. Projects like CoffeeScript and Script# do not have the time or resources to put into multiple source map generators. Then web developers will be faced with the problem that their tool of choice only generates source maps for chrome, but not for firefox or IE, or the other way around. Or, compiler writers will simply forgo source map compilation altogether because nobody can agree on a specification. The best case scenario is that they are similar enough that one could write a tool to translate a source map from one format to another, but that could result in a loss of information.
So, it would be better for all stakeholders involved if IE implemented the google standard, or else worked with both google and the Mozilla team to improve the standard together before implementing it, possibly even formalizing it into a web standards body proposal together. In this ecosystem, there is only room for one specification, so it's better to work together on it and not introduce a competing format just for the sake of inventing something in-house.
Aug 12, 2011 at 8:06 PM
Love these mango vids! If any microsofties are looking for a fun mango project, would love to see a telnet client for wp7 mango showing off both sockets support and the rich text control... Hehe
If I may recommend my own apps, I have two on the marketplace right now:
The first is Giggle Pad, a fun/educational game for very young children (around 9 months and up). You tap the screen (or press keys on your phone keyboard, if you have one) for random letters, numbers, or shapes in different colors and the app speaks the letter/number/shape and the color. Or, you can drag your finger across the screen for a colorful fireworks effect accompanied by a song. Giggle Pad also includes a "play phone" mode with a large on-screen keypad that speaks and sings songs when you press the keys. Here is the deep link:
My second app is a little utility called Pixel Checkup. This app helps you find and track dead pixels on your screen by completely filling it with white, black, red, green, or blue (this makes it easier to see the screen damage). You can also have it slowly cycle through these colors, making it even easier. If you find a dead pixel, you can touch the screen and a colored marker will be placed and saved, so you can check it again later to make sure the damage hasn't spread to adjacent pixels. The trial mode also functions as a free flashlight app when you bring up the white color. This app is also available in French, Spanish, and Italian. Here is the deep link:
Oct 19, 2010 at 8:30 AM
Can't wait for the Hot Apps show either!