31–40 of 76 posts
Earlier quoted context omitted.
Not to mention that pausing still puts it in a weird state where hitting play doesn't make it pick up again. You have to slightly move the knob.
If I recall it correctly, flash versions also have this problem (intermittently).
WP7 might be the first to have a good default browser for HTML5, and that kind of dumbfounds me. Get on the ball, Apple and Google. I know it's in your best interests to keep the more powerful stuff out of your mobile browsers, but the sooner the better.
I thought I read somewhere last year that Flash was dead. Yet, Flash is still here. I think everyone can agree that we all understand that Flash is on its way out as a tool for websites. Those stupid intros and Flash menus are already dying out thanks to javascript. Nothing to do with HTML5 at all. So HTML5 will offer us similar capabilities to Flash using Canvas. Does that mean in a few years we can start hating on…
Earlier quoted context omitted.
>At all. I find that to be a disingenuous or at least off topic insult. Is it even possible to insult a multinational company? My point is that the article suggests that Apple is a big friend to HTML5, and that the growth of HTML5 will be in large part due to Apple's "massive support". I do not believe that Apple is a "massive" supporter of HTML5. Apple's first priority is securing their own walled garden, not HTML5.…
Again, how is having a native platform in any way shape or form hostile towards HTML5? The only possible way I could understand your paranoia was before Apple turned on Nitro for their embedded web views. Now that they've done that, there's simply no reason to believe that they would deprecate their browser or fork HTML5. Besides the article doesn't say that they're a big supporter (though I think they are: WebKit, S…
There is no reason why App Store apps could not be written with HTML5. It works offline. It has local storage. Apps written in such a way could work on iOS, Android, WM, WebOS... the whole lot. Yet they are not allowed in the App Store (or Android Market, etc. etc.)- this holds back HTML5. (and of course they would benefit from it- users go straight to the App Store to download apps. Offline web sites just don't have the same understanding)
I am not suggesting that the manufacturers throw out their existing native layers- there are times (3D games, etc) where they are entirely appropriate. But while they are the only option, developers are forced into walled gardens when writing apps. I can't work out how anyone would perceive that as a good thing.
“I think the disappearance of Flash is closer than
people think,” ABI senior analyst Mark Beccue said
in a press release accompanying the data.
Earlier quoted context omitted.
Again, how is having a native platform in any way shape or form hostile towards HTML5? The only possible way I could understand your paranoia was before Apple turned on Nitro for their embedded web views. Now that they've done that, there's simply no reason to believe that they would deprecate their browser or fork HTML5. Besides the article doesn't say that they're a big supporter (though I think they are: WebKit, S…
At this point I really don't know what to reply- I really don't understand how on earth you'd read the comment I posted and interpret it as "Apple should scrap Mobile Webkit". You seem to have interpreted my comments to be the exact opposite of what I was actually saying. How does "I think Apple are holding back HTML5" (my original comment) end up meaning "I want Apple to remove HTML5 features from their phones"? The…
You can absolutely publish fully functional HTML5 apps right now and any user on any mobile platform can use them. Even more, you can make simple Web View wrapper and publish them to Market, App Store, etc. Surely, surely, you're not really sitting there saying they have to build some new manifest and packaging format to support web apps... in their NATIVE application store, right? The entire point of web apps is that you don't need the concept of an "app". The app is the webpage as it's displayed in the browser. If you want to avoid that perception issue, then use an embedded web view wrapper.
My point was that all of these functionalities and abilities are in existence RIGHT NOW in (at least) the WebKit browsers. You're acting like it's not possible now, or that it won't be in the future. My point was that your accusations imply that Apple/Google/etc will, at some point in the future, go back and remove the Location API or Local Storage APIs or future Device APIs from their browsers... (since that's the only way your accusations make any sense).
You continue to act like the native platform or native app store somehow impedes the ability to use the browser or web views, which is just either above my head or just plain wrong.
Youtube's HTML5 player is still very alpha and poorly designed (still no fullscreen?). It has hardly changed in over a year since it was released. I question Google/Youtube's commitment to moving to HTML5.
YouTube was founded on the idea that people could record via webcam and post videos immediately with no knowledge of video files, etc.
How is HTML5 solving this problem for YouTube?
It's amazing how - I think at least - the web is moving away from framework based technologies to HTML, CSS and Javacsript as primary sources. Indeed, Windows 8 is pushing support for such technologies and actually supporting a move away from framework based technologies to the HCJ combo. Even now with the popularity of HTML5 API's and NodeJS - the push away from traditional frameworks is becomming evident. Just look…
There are many kinds of frameworks in many languages and technologies.
“I think the disappearance of Flash is closer than people think,” ABI senior analyst Mark Beccue said in a press release accompanying the data. This is from the mouth of someone who doesn't really understand what Flash is, apparently. HTML5 may dethrone Flash as the defacto video delivery system. But, to say HTML5 completely obliterates Flash is...kinda hyperbolic in a way.
-Video. (Mwoah, only non-WebM video, can't really count this one)
-Webcam
(thanks garethsprice)
-Simultaneous sounds (thanks AndyJPartridge)
-Cross-browser support (browsers interpreting HTML5 differently)
-???
-Games (see Angry Birds)
-3D hardware acceleration (both have the same security issues exposing shaders)
-2D Hardware acceleration
-Open
-Cross-browser support (flash has it's update/versioning problems)Earlier quoted context omitted.
At this point I really don't know what to reply- I really don't understand how on earth you'd read the comment I posted and interpret it as "Apple should scrap Mobile Webkit". You seem to have interpreted my comments to be the exact opposite of what I was actually saying. How does "I think Apple are holding back HTML5" (my original comment) end up meaning "I want Apple to remove HTML5 features from their phones"? The…
I really don't mean to sound rude, but you're not reading what I'm writing and I'm honestly not sure that you understand HTML5 or the capabilities that current mobile devices have in the HTML5 front. You can absolutely publish fully functional HTML5 apps right now and any user on any mobile platform can use them. Even more, you can make simple Web View wrapper and publish them to Market, App Store, etc. Surely, surel…
Throughout this entire discourse (and I'd challenge the claim that you've "tried to be nice", unless you just didn't try very hard) you've thrown out various accusations of what I think, then dismantled them- despite me having never suggesting anything of the sort in the first place.
Why on earth would I accuse Apple/Google of planning to remove HTML5 APIs? I genuinely have no idea why you are projecting these ideas. My point is that HTML5 could be a first-class citizen when it comes to app making. It is not. And the fault for that lies with the phone manufacturers. Therefore, in my mind, Apple does not have "massive support" for HTML5.
But hey, let's leave it here, while you're trying to be nice. I'm not sure I'm interested in finding out how condescending you'll be when you aren't.