6 ms·

Adobe needs to embrace HTML 5 and start making great tools around the HTML 5 runtimes. Flash, the runtime makes them nothing. Yes, the build tools around Flash,

by zarski 17y ago

Adobe needs to embrace HTML 5 and start making great tools around the HTML 5 runtimes. Flash, the runtime makes them nothing. Yes, the build tools around Flash, however, they need to stop their belly aching around HTML,JS,and CSS and learn to embrace and profit.

nailer 17y ago
And that's what I really want to hear from John - not arguing over who did what, but a simple statement along the lines of: 'Adobe will modify existing tools, or create new tools that allow content creators to do 2D and 3D drawing, and/or video, using Canvas and HTML Video, with the output not relying on Adobe Flash technologies ' or: 'Adobe will not modify existing tools, or create new tools that output to Canvas and HTML Video' Either answer shows whether they're committed to a rich web with these features built in as standard.
amadiver 17y ago
Their thoughts exactly: http://blogs.adobe.com/jnack/2009/10/sneak_peek_ai_fl_dw_canvas.html http://blogs.adobe.com/jnack/2009/10/sneak_peek_ai_fl_dw_can...
fnid2 17y ago
That they aren't doing this is why Jobs called them lazy. They are lazy. There is no reason it should take 40% of the CPU to show a video in a flash embed on a laptop. If they can't optimize any better than that, how are they ever going to see success on mobile devices?
- rortian 17y ago
  It's hard not to be condescending about this but this is super basic: Video is hard if it is not hardware accelerated. Apple refuses to provide a public api for this, so flash video needs a lot of CPU time on OSX. All cell phones that allow flash video will have hardware acceleration and will not have a problem with it.
  - blasdel 17y ago
    Please don't parrot Nack's talking points. Flash on Windows has only had hardware accelerated video decoding for about 6 months, on minority hardware, in beta versions of Flash 10.1. It hasn't been released yet. No cellphones with full Flash players have been shipped yet either, despite breathless press releases going back years. Unaccelerated Flash on Windows handles video decoding just fine, and has for years, with no special hardware or APIs available. It's squarely Adobe's problem.
    - rortian 17y ago
      It seems to be the users of OSX problem. Window's is much more flexible about allow the access to hardware. I wasn't parroting talking points...I just have experience with video on linux unaccelerated and it is not fun at all. The direct acceleration of video decoding is relatively new but I'm sure the Android versions with use this feature. Thanks for info. Chill on the paranoia .
      - blasdel 17y ago
        Yes, hardware acceleration is nice, but the lack of raw access to it isn't the issue here. Flash has always worked fine on Windows without it. Apple's position is that if you want to decode+display video, it would be best to use the QT API with the codecs they ship, and get acceleration for free where available. Given Adobe's track record, they don't want them mucking about in the bowels of the video drivers. Accelerated video drivers were the number one location of kernel panics on Windows XP, so Microsoft spent a lot of effort to rearchitect the system in Vista, where it now causes a "kernel oops" instead, and the user just gets a 2s pause and a taskbar notification while the driver reloads. They took a lot of grief from users over the slightly decreased performance and the transition when their drivers didn't work at all, but it was the right thing for them to do. Apple has not yet needed to invest in this. The Flash plugin is by far the most common cause of application crash reports on Mac OS X. Nearly every user experienced them, I used to get them on a daily basis! Very few of their users have ever seen the OS X kernel panic screen, especially without having failing hardware, and Apple would like to keep it that way.
  - 17y ago
hristov 17y ago
Riiight. And suppose you want them to compete with any other unwashed commoner that decides to make his/her own tools for HTML 5. I see you have never been to business school.

by zarski 17y ago

nailer 17y ago

And that's what I really want to hear from John - not arguing over who did what, but a simple statement along the lines of: 'Adobe will modify existing tools, or create new tools that allow content creators to do 2D and 3D drawing, and/or video, using Canvas and HTML Video, with the output not relying on Adobe Flash technologies ' or: 'Adobe will not modify existing tools, or create new tools that output to Canvas and HTML Video' Either answer shows whether they're committed to a rich web with these features built in as standard.

amadiver 17y ago

Their thoughts exactly: http://blogs.adobe.com/jnack/2009/10/sneak_peek_ai_fl_dw_canvas.html http://blogs.adobe.com/jnack/2009/10/sneak_peek_ai_fl_dw_can...

fnid2 17y ago

That they aren't doing this is why Jobs called them lazy. They are lazy. There is no reason it should take 40% of the CPU to show a video in a flash embed on a laptop. If they can't optimize any better than that, how are they ever going to see success on mobile devices?

rortian 17y ago
It's hard not to be condescending about this but this is super basic: Video is hard if it is not hardware accelerated. Apple refuses to provide a public api for this, so flash video needs a lot of CPU time on OSX. All cell phones that allow flash video will have hardware acceleration and will not have a problem with it.
- blasdel 17y ago
  Please don't parrot Nack's talking points. Flash on Windows has only had hardware accelerated video decoding for about 6 months, on minority hardware, in beta versions of Flash 10.1. It hasn't been released yet. No cellphones with full Flash players have been shipped yet either, despite breathless press releases going back years. Unaccelerated Flash on Windows handles video decoding just fine, and has for years, with no special hardware or APIs available. It's squarely Adobe's problem.
  - rortian 17y ago
    It seems to be the users of OSX problem. Window's is much more flexible about allow the access to hardware. I wasn't parroting talking points...I just have experience with video on linux unaccelerated and it is not fun at all. The direct acceleration of video decoding is relatively new but I'm sure the Android versions with use this feature. Thanks for info. Chill on the paranoia .
    - blasdel 17y ago
      Yes, hardware acceleration is nice, but the lack of raw access to it isn't the issue here. Flash has always worked fine on Windows without it. Apple's position is that if you want to decode+display video, it would be best to use the QT API with the codecs they ship, and get acceleration for free where available. Given Adobe's track record, they don't want them mucking about in the bowels of the video drivers. Accelerated video drivers were the number one location of kernel panics on Windows XP, so Microsoft spent a lot of effort to rearchitect the system in Vista, where it now causes a "kernel oops" instead, and the user just gets a 2s pause and a taskbar notification while the driver reloads. They took a lot of grief from users over the slightly decreased performance and the transition when their drivers didn't work at all, but it was the right thing for them to do. Apple has not yet needed to invest in this. The Flash plugin is by far the most common cause of application crash reports on Mac OS X. Nearly every user experienced them, I used to get them on a daily basis! Very few of their users have ever seen the OS X kernel panic screen, especially without having failing hardware, and Apple would like to keep it that way.
- 17y ago

hristov 17y ago

Riiight. And suppose you want them to compete with any other unwashed commoner that decides to make his/her own tools for HTML 5. I see you have never been to business school.