[citation][nom]jacekring[/nom]They did say that it will use the Android Kernel, so the HTML5 will not directly interact with hardware. There will be an interface layer between the Kernel and the HTML5 interface, probably a parser.Oh btw, I thought that the Android Kernel was the Linux v2.6 Kernel....so it's kind of stupid to call it the "Android Kernel" because Android doesn't have it's own kernel, it uses the Linux Kernel.[/citation]
cool
still won't trust it, the easiest example in recent history is OSX, which in its original release had some really scary bugs that apple refused to acknowledge, if you want another example there where certain versions of HTC's touch flow interface (is that what its called?) that could be messed up with a single text message if you knew the right string of characters to send.
My issue isn't with the implantation, i'm sure they will do all they can to make it secure. Its being a first adopter, and taking a risk with a device that will take center stage for my calls, and my social network accounts.
A lot more can be lost, and a lot more will be at risk when this product comes to market. I support HTML 5, but i'm not sure how far companies should extend that functionality vs how familiar they are with HTML5. It is new, and I think that developers should spend more time becoming familiar with HTML5 development (bring out some cool apps that people feel the need to go to), before talking about extending its functionality into more hardware, specifically the data and voice functions on the device.
Its new, and I stand by my opinion, unless there's a really beefy layer of security between a peace of code that can run on my browser, and as a program on my phone, I wont trust it.