Mobile Flash Fail: Weak Android Player Proves Jobs Right
31–40 of 194 posts
Re: Mobile Flash Fail: Weak Android Player Proves Jobs Right
#32Earlier quoted context omitted.
HTML5 is cool but it's not the end-all. You have a whole set of new issues to deal with when you use HTML5. You have to worry about cross-browser compatibility and specific rendering bugs, whereas Flash authors don't. You have to rely on the slow JavaScript VMs included in even the fastest browsers (even the "fast" JS VMs are still rather slow), and then you have IE, which is still used by > 50% of internet users, of…
"even 'fast' JS VMs are still rather slow" Compared to C, Java, OCaml, and so forth, perhaps. Compared to Ruby, Python, and PHP - not so much. (take a look at the v8 entry. and this is from '09 - v8 has seen some performance improvements since then) http://blog.gmarceau.qc.ca/2009/05/speed-size-and-dependabil...
It would be interesting, though, if someone could point me (and everyone else) to a reasonable, credible comparison of HTML5+JS vs. Flash vs. Silverlight.
Re: Mobile Flash Fail: Weak Android Player Proves Jobs Right
#33For a blog called "the geek's geek" it sure sounds like the guy needs some technical support because many others report a completely better experience. Also, it's a fracking mobile phone you are holding in the palm of your hand and you want it to be as powerful as a desktop experience? Reality check!
My iPhone 3G's processor is faster than one of my laptops (that I used on a daily basis, but recently retired it due to buying a new Starling Netbook). You're damn right it better perform just as well!
Re: Mobile Flash Fail: Weak Android Player Proves Jobs Right
#34Strongbad episodes and casual flash games run perfectly. The small amount of video I have tried seems fine - Youtube via the inline flash player (not launching the separate application) and flash player video porn.
The argument that Jobs was right because flash video sucks on a phone seems silly - weren't we suspecting that flash games were what Apple were trying to keep off their ecosystem?
Re: Mobile Flash Fail: Weak Android Player Proves Jobs Right
#35Earlier quoted context omitted.
HTML5 is cool but it's not the end-all. You have a whole set of new issues to deal with when you use HTML5. You have to worry about cross-browser compatibility and specific rendering bugs, whereas Flash authors don't. You have to rely on the slow JavaScript VMs included in even the fastest browsers (even the "fast" JS VMs are still rather slow), and then you have IE, which is still used by > 50% of internet users, of…
"even 'fast' JS VMs are still rather slow" Compared to C, Java, OCaml, and so forth, perhaps. Compared to Ruby, Python, and PHP - not so much. (take a look at the v8 entry. and this is from '09 - v8 has seen some performance improvements since then) http://blog.gmarceau.qc.ca/2009/05/speed-size-and-dependabil...
http://en.wikipedia.org/wiki/Actionscript
Adobe's had a JIT Actionscript compiler for years and it's really quite fast.
Re: Mobile Flash Fail: Weak Android Player Proves Jobs Right
#36I would give anything for someone to explain to me why the right move for Adobe wasn't to simply accept HTML5, pivot from Flash to making killer HTML5 authoring tools, and maybe even provide a way for people to take their existing Flash projects and repurpose them to HTML5? How would that have been worse then trying to wedge Flash where it doesn't belong?
The much glossed-over answer is that JavaScript and HTML just isn't a good environment for rich app development, for many reasons. One "elephant in the room" kind of issue is that JavaScript's object system is not acceptable to most programmers, and most programmers require classical OOP. Even prototype system fanatics probably would have to admit that the current state of JavaScript doesn't work very well, with its…
I hear about Chrome OS every single day, because I follow its development. Many hardware manufactures will be releasing Chrome OS netbooks in November / December of this year. Google doesn't generally hype things before they are available to consumers, so there's no reason to expect lots of Chrome OS discussion while it's still in development.
Google is still very hardcore about JavaScript/HTML5 development.
Re: Mobile Flash Fail: Weak Android Player Proves Jobs Right
#37For a blog called "the geek's geek" it sure sounds like the guy needs some technical support because many others report a completely better experience. Also, it's a fracking mobile phone you are holding in the palm of your hand and you want it to be as powerful as a desktop experience? Reality check!
> Also, it's a fracking mobile phone you are holding in the palm of your hand and you want it to be as powerful as a desktop experience? Reality check! My iPhone 3G's processor is faster than one of my laptops (that I used on a daily basis, but recently retired it due to buying a new Starling Netbook). You're damn right it better perform just as well!
You can't compare different CPU architectures by the number of hz. Desktop (=laptop in this case) processors are out-of-order power-sucking beasts compared to the power sipping CPU in your phone and other devices.
Watts vs. milliwatts in comparison.
Re: Mobile Flash Fail: Weak Android Player Proves Jobs Right
#38Re: Mobile Flash Fail: Weak Android Player Proves Jobs Right
#39Adobe is seriously doing it all wrong. They have to open-source the Flash Player and everything around it now. They can keep the IDE proprietary if that floats their boat, it's just a premium authoring tool, but the only way to save Flash is to open-source like NOW. HTML5 is still young enough that an open Flash Player and standard and protocol (RTMP) would effectively kill it. Open-sourcing would open so many doors.…
Re: Mobile Flash Fail: Weak Android Player Proves Jobs Right
#40I would give anything for someone to explain to me why the right move for Adobe wasn't to simply accept HTML5, pivot from Flash to making killer HTML5 authoring tools, and maybe even provide a way for people to take their existing Flash projects and repurpose them to HTML5? How would that have been worse then trying to wedge Flash where it doesn't belong?
If you can show me how to make audiotool.com or even something like captainforever.com in HTML5 I think I'll begin to see where you're coming from, but there are plenty of things Flash does that HTML5 does not. To flip the switch from Flash 10 to HTML5 would be cutting off a lot of functionality. Saying HTML5 should replace Flash is like saying HTML5 should replace JPGs.
Really? Can you mention any specifics? I do not think there are any things that Flash can do that HTML5 cannot.
Have you seen Or So They Say? http://xplsv.com/prods/demos/xplsv_orsotheysay/