Interesting, now it looks like meant to be useful client-side cross-scripting tools are about to be abused and tracked by popular Antivirus software: http://www.sophos.com/en-us/threat-center/threat-analyses/viruses-and-spyware/Andr~Cova-A.aspx
The whole "Java on the Client used by Malware" outcry as opposed to "Java on the Server is Safe and the Foundation of Multi-Billion Dollar Businesses" does seem to apply to a Device Recognition on the Client using some sort of Scripting vs. Device Recognition on the Server using a Device Definition Repository choice, too. At least in some cases. Maybe it's time to shift priorities and resources poured into one side of this equation a bit?[?] Especially on iOS while PhoneGap/Cordova seems to have been mostly accepted there, Adobe first and foremost will remember the ongoing security threats by client-side runtimes like Flash, Shockwave, ColdFusion and whatever else is or was out there... Android, too, with version 4 Flash was practically killed on Android recently. Could be, while true native apps won't die and in many cases are the best alternative, that companies and services who wish to address multiple platforms have to rethink portable apps over a security threat, this kind of Scripting always had an always will be, especially if more and more devices use such run-times [?] A good reason not to let DeviceMap die, there seems to be demand and it may even grow in certain areas[?] Regards, Werner
