Stories
Slash Boxes
Comments

SoylentNews is people

posted by takyon on Thursday December 03 2015, @01:37AM   Printer-friendly
from the flashy-exit dept.

Flash continues to sink away into the shadows:

Adobe is finally ready to say goodbye to Flash. In an announcement last night, Adobe said that it will now "encourage content creators to build with new web standards," such as HTML5, rather than Flash. It's also beginning to deprecate the Flash name by renaming its animation app to Animate CC, away from Flash Professional CC.

[...] By acknowledging that Flash is dying, Adobe is able to better position its animation tools for the future. Flash Professional CC is already capable of creating HTML5 content — in fact, it already represents a third of all content created in the app, according to Adobe. By taking up the name Animate CC, Adobe is able to sell Flash Professional CC as a general animation tool, rather than a tool geared toward Flash. The name change will take effect early next year.

-- submitted from IRC


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Informative) by SuperCharlie on Thursday December 03 2015, @02:30AM

    by SuperCharlie (2939) on Thursday December 03 2015, @02:30AM (#271125)

    I was there in the beginning. When it was fresh and new and pitted against animated gifs could do in a few K what took gif hundreds. And then the creep started. Buttons, actions, scripting, it grew into an abomination to web development and worse, security. The never ending feature bloat and next big thing killed flash.

    Starting Score:    1  point
    Moderation   +1  
       Informative=1, Total=1
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 2) by takyon on Thursday December 03 2015, @05:05AM

    by takyon (881) <reversethis-{gro ... s} {ta} {noykat}> on Thursday December 03 2015, @05:05AM (#271204) Journal

    SWF can get big, especially since it can contain raster images, but it has always been the CPU cycles that seemed to have made it so bad. A 10 kilobyte swift can churn CPU just fine using scripting.

    --
    [SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]