I agree, this is a good thing. Let the use of SSN collapse as a means of granting information. Trying to hide a small number from birth to death is ridiculous. It's equally aweful that companies can claim that you did something because that number was used for the transaction.
The divide still exists, Microsoft is simply trying to integrate the tools that designers and developers use.
In the current paradigm designers create non-functional art. Then programmers recreate that art in code. Being programmers and not designers they often don't really see all the details and subtleties, so this is a very difficult back and forth process. Finally the programmers create the engines behind the interface so the program can do the heavy-duty work.
The new paradigm removes that middle step. Designers develop functional art with graphical tools that are natural and familiar. Then the programmers put the engines directly behind what the designers create.
I encountered this video in an article on ArsTechnica. It is a great explanation from the Sparkle development team, complete with hands on demonstrations. Personally, I'm very excited.
Slashdot Mirror
I agree, this is a good thing. Let the use of SSN collapse as a means of granting information. Trying to hide a small number from birth to death is ridiculous. It's equally aweful that companies can claim that you did something because that number was used for the transaction.
V = velocity of travel in units traveled over time V = [d(unit)]/[d(time)] Let dm = my percieved time delta Let dt = standard time delta V = dm/dt
In the current paradigm designers create non-functional art. Then programmers recreate that art in code. Being programmers and not designers they often don't really see all the details and subtleties, so this is a very difficult back and forth process. Finally the programmers create the engines behind the interface so the program can do the heavy-duty work.
The new paradigm removes that middle step. Designers develop functional art with graphical tools that are natural and familiar. Then the programmers put the engines directly behind what the designers create.
I encountered this video in an article on ArsTechnica. It is a great explanation from the Sparkle development team, complete with hands on demonstrations. Personally, I'm very excited.