In that case, the store could decide to file a criminal complaint against the child.
The store doesn't have standing to file a criminal complaint against the child, it was not their card. Quite plainly they failed in their duty to ensure that the person using the card was the authorized cardholder. The contract with the credit card company is quite clear that it is the store that is liable in this case.
Nope, people *think* they only authorized one payment, because they don't know how the system works. What they actually are authorizing is a 30 minute windows of purchases.
I'd be very surprised if their agreement with the credit card companies allowed open ended authorizations like this. Certainly the consumer laws in many countries do not, which would leave the credit card companies holding the ball, something they try very hard to avoid in their agreements.
Also google gives you the option of getting the app off the play website and downloading it.
I think you mean the option to make the purchase on the website and push the app to your phone. But are you sure that makes any difference to the 30 minute window?
Also, at the time the iPhone was being developed, a number of other vendors were developing similar devices - Apple just happened to get to market slightly before everyone else and did their usual job at marketing (Apple are *really* good at marketing).
Basically, Apple made a good call on the timing of reentering the market, at the time that the hardware became available to make a smooth UI with a touchscreen that was suited to operating with fingers rather than a stylus. It also had the advantage of being both a hardware and software company, while other hardware companies were mostly relying on Microsoft to catch up with the capabilities of the hardware. They also made some good calls on which new technologies to adopt and which to wait for - at the time the iPhone launched, smartphones had moved from 320x240 displays to 640x480 and were in the process of moving to 800x480 with the new support for higher resolutions in Windows Mobile 6. Apple chose 480x320 initially, which was an important part of getting the UI graphics and video playback working well with the ARM11 processors that were available at the time.
I've played with some VM's but there is a problem -- limited access to the actual system hard drive.
I don't know what VMs you've played with, but I once managed to completely screw up my Windows installation by a slip of the key in a Linux VM - putting
Seems credible to me that they could take second place once Blackberry is fully gone, if they can crack the Asian market, where right now you're right.
Microsoft will never "crack" the Asian market, they plainly just don't understand it. For instance, in the most linguistically diverse region of the world, they ship a version of Windows 8 called "Single Language Edition". And then they wonder why Asia is still mostly running off pirated copies of earlier versions.
Apple is late to the game, because Google is working on something.
You obviously epically FAILED to read the rest of my post. Stalker.
Being long in the tooth I do all my web development via Perl using my own nice call back templating engine and of course CGI.pm.
Having seen some Perl web scripts that very much do not meet this description, and some PHP that was nicely templated I can say with confidence that it is not the language that is at fault here.