I'm surprised such equipment isn't found as a threat to national security. How can a regular Joe have any use for atomic clocks while they could be used for terrorist applications.
Instead of a simple pressure sensor I would see a lot more potential in the technology if it paired with a wireless verification protocol, to ensure that the device indeed is capable and willing to accept the charge. This would help avoid misbehavior in cases such as throwing your keys on the pad(which was used as an example of concern in an earlier post).
As a long time GNU/Linux user I'm used to my system being like a big pile of Legos, with different pieces doing different things and fitting together by a certain ruleset. This allows me to do a lot of things that aren't there straight out of the box.
Microsoft's approach is to provide one software for a particular purpose that will, hopefully, be the complete solution to the need. Their software comes out as an integration the system's building blocks that can't be broken down or modified for a particular need. Unfortunately that "one solution fits all" approach is quite narrow minded and I can't help feeling oppressioned by the company that makes its decisions without asking, but leaves no the user no possibilities to transform the software to their need. And, a lot of their decisions are downright counter-intuitive(like a file open dialog magically transforming into a network connect dialog by switching the displayed file type to ODBC).
Most users will be happy with any interface that involves little to no learning to pull pictures out of their cameras and burn CDs/DVDs, and in most cases Microsoft can provide them with that.
Slashdot Mirror
Shouldn't atoms be regulated or something?
Does this mean Windows gets multiuser support?
How about "Rusty Russell"?
Instead of a simple pressure sensor I would see a lot more potential in the technology if it paired with a wireless verification protocol, to ensure that the device indeed is capable and willing to accept the charge. This would help avoid misbehavior in cases such as throwing your keys on the pad(which was used as an example of concern in an earlier post).
As a long time GNU/Linux user I'm used to my system being like a big pile of Legos, with different pieces doing different things and fitting together by a certain ruleset. This allows me to do a lot of things that aren't there straight out of the box.
Microsoft's approach is to provide one software for a particular purpose that will, hopefully, be the complete solution to the need. Their software comes out as an integration the system's building blocks that can't be broken down or modified for a particular need. Unfortunately that "one solution fits all" approach is quite narrow minded and I can't help feeling oppressioned by the company that makes its decisions without asking, but leaves no the user no possibilities to transform the software to their need. And, a lot of their decisions are downright counter-intuitive(like a file open dialog magically transforming into a network connect dialog by switching the displayed file type to ODBC).
Most users will be happy with any interface that involves little to no learning to pull pictures out of their cameras and burn CDs/DVDs, and in most cases Microsoft can provide them with that.
Power users need more.