Slashdot Mirror


After Twenty Years of Flash, Adobe Kills the Name (thestack.com)

An anonymous reader writes: From January 2016, Adobe Flash will be renamed to 'Adobe Animate CC', killing one of the most unfortunate names in web security as the company pushes the product further and further to HTML5 output. Adobe's release about the update, which will form part of the annual Creative Cloud upgrade, states that a third of all material output from the program is now HTML5. The transitional HTML5 Adobe animation program Edge Animate will be replaced by the renamed Flash product.

21 of 125 comments (clear)

  1. A rose by any other name... by RavenLrD20k · · Score: 5, Insightful

    A Rose by any other name still smells as sweet.

    Adobe Flash by any other name still reeks of shit.

    1. Re:A rose by any other name... by gstoddart · · Score: 2

      As long as I can turn it off, I don't give a crap what they call it.

      Flash has pretty much had at least one gaping security hole for every month of that 20 years.

      And in the 19.5 years I've been disabling/uninstalling/blocking it, I've never felt like I was missing anything. The sooner Flash finally dies and goes away the better.

      --
      Lost at C:>. Found at C.
    2. Re:A rose by any other name... by slashkitty · · Score: 4, Insightful

      I'm guessing you're not turning off HTML 5.

      --
      -- these are only opinions and they might not be mine.
    3. Re: A rose by any other name... by jd2112 · · Score: 2

      Adobe Crash.
      It even rhymes with Flash.

      --
      Any insufficiently advanced magic is indistinguishable from technology.
    4. Re:A rose by any other name... by Solandri · · Score: 4, Informative

      Flash was originally created as an artist's tool - to allow streaming animation which didn't take up as much bandwidth by only transmitting backgrounds and sprites once and animating them on the client, rather than streaming raw video. For that purpose it's a fantastic tool, with several TV shows and animated movies still being created with it.

      Flash didn't ask to become the de facto scripting language for the web. It only became that because the HTML standard lacked scripting and programming capability which Flash provided. It was a security disaster because it was only ever intended to be an artist's tool and little thought went into making it secure. If you want to blame someone, blame the folks in charge of the HTML standard. They dragged their feet for over a decade, and didn't update HTML to provide many of the capabilities Flash provided until HTML5. HTML 4.01 was standardized in Dec 1999. HTML 5 was standardized in Oct 2014. It should have been made standard in 2001-2003.

    5. Re:A rose by any other name... by ilsaloving · · Score: 2

      No, Flash didn't ask to be the de facto scripting language. But it become so, all the same. And Adobe ran with it, making it more and more featureful, while giving not giving security any thought at all.

      Saying that they didn't ask for it is a cop out. HTML's lack of progress was an opportunity for Adobe, and Adobe pushed Flash as hard as they possibly could, doing everything they could to make Flash utterly ubiquitous. Adobe is *absolutely* to blame for the shitpile that is Flash. They've had more than enough time and opportunity to clean things up. The fact of the matter is that they *chose* not to fix it.

    6. Re:A rose by any other name... by Bogtha · · Score: 2

      Flash didn't ask to become the de facto scripting language for the web. It only became that because

      Flash has never been the de facto scripting language for the web. That has always been JavaScript.

      the HTML standard lacked scripting and programming capability which Flash provided.

      No, the HTML standard didn't lack scripting capability, it offered hooks for scripting languages, and they were in use since before Flash existed.

      blame the folks in charge of the HTML standard. They dragged their feet for over a decade, and didn't update HTML to provide many of the capabilities Flash provided until HTML5. HTML 4.01 was standardized in Dec 1999. HTML 5 was standardized in Oct 2014. It should have been made standard in 2001-2003.

      Wow, that's a total misrepresentation of what happened. Client-side scripting was not part of HTML. HTML provided hooks, scripting languages used those hooks to integrate into a page. This is an entirely sensible separation of concerns between content and behaviour. At some point, client-side scripting got glommed onto the HTML 5 specification. But in-between those two points, there were huge amounts of progress with client-side scripting.

      You make it sound as though non-Flash client-side scripting arrived when HTML 5 brought it forth. It was always there, and always making progress, since before Flash existed. HTML 5 was merely the point at which they decided to define some things in the HTML specification rather than separate specifications.

      --
      Bogtha Bogtha Bogtha
  2. Ah, yes, a standard security technique. by jeffb+(2.718) · · Score: 5, Insightful

    I think I remember that from one of my computer-security classes. Sanitize all your inputs, do length checks to avoid buffer overflows, and if those don't work, change your product's name.

    1. Re:Ah, yes, a standard security technique. by Anonymous Coward · · Score: 3, Funny

      Unfortunately, they left in the "Adobe" part.

    2. Re:Ah, yes, a standard security technique. by Dracos · · Score: 2

      And added the CC part.

  3. headline and summary wrong by Anonymous Coward · · Score: 5, Informative

    they are not killing the flash name; the new version of their *creation* package is renamed to Animate from Flash Professional since it outputs HTML5 in addition to SWF; this is not related to the client side SWF ecosystem

  4. This Is The Authoring Tool, Not The Plugin by American+AC+in+Paris · · Score: 5, Informative

    They're renaming the authoring tool, which is currently known as Flash Professional CC. It appears that the Flash Player will remain just that.

    This makes perfect sense, as Flash Professional CC is increasingly being used to generate media that targets HTML5, not Flash, as output. Renaming Flash Professional CC to Animate CC eliminates the whole need to do the song and dance of "we're talking about Flash the authoring environment, not Flash the plugin" to non-technical audiences.

    --

    Obliteracy: Words with explosions

  5. Phew by Opportunist · · Score: 2

    For a brief moment I was worried they might have killed Flash. Then I noticed they only retired the name 'cause it was already pretty much synonymous of "malware installer".

    For a moment I was worried about my job security. Please, Adobe, don't scare us IT security guys like that!

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  6. What really? by roc97007 · · Score: 2

    What I'm reading from this is that Edge Animate, Adobe's HTML 5 tool, will be renamed Adobe Animate CC, and will gain some (probably funky) backwards compatibility to Flash.

    But it's not as sexy when you put it that way.

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  7. Linux support, PLEASE by pz · · Score: 4, Interesting

    I don't care what they name it, within reason. It's a product / tool / whatever. Does it work? Good.

    In particular, will they PLEASE PLEASE PLEASE update the Reader application under Linux to support some kind of contemporary animation that's supported on other platforms as well? I don't care if it's Flash, HTML5, AVI, MOV ... I just don't care. It doesn't matter. What matters is that I can display animations within a PDF, and be certain that they will play for others on Windows or iOS as well. Right now, as a Linux user, I don't have that ability, really.

    --

    Put my fist through my alarm clock with its ding-dong death inside my ear. - The Blackjacks.
  8. Re:...would smell as shitty as any browser by Grishnakh · · Score: 5, Interesting

    And yeah, there's NoScript... but that tends to limit the web's basic functionality.

    NoScript is a HUGE improvement, in my experience. However, it's also a big pain in the ass to use, so I wouldn't foist it on my wife's computer for instance. What works well is to set the selection to whitelist scripts coming from the site's own domain, but after that you have to get good at manually enabling other domains, usually ones with "cdn" in them since most big sites deliver videos and such from affiliated CDN domains. If that doesn't work, however, then you're resorting to guessing; there's been a few times I've just started up an alternate browser that doesn't have NoScript installed just to look at one site, but this is rare. For the most part, NoScript is really helpful and speeds things up a lot, but it's really not that easy to use because the situation with JavaScript is such an utter mess, with dozens of scripts on every page it seems.

  9. Re:...would smell as shitty as any browser by Anonymous Coward · · Score: 4, Insightful

    The FBI attacked Tor users this way last year; that attack is only known to the public because it was revealed in court proceedings. I don't know about you, but I'm going to assume there are still other JS exploits out there being used (by good and bad guys) that haven't yet become public.

  10. Re:...would smell as shitty as any browser by Grishnakh · · Score: 2

    If you allow everything by default, you're not going to get any benefit from it whatsoever. You might as well just use uBlock Origin so you avoid all the ads, but it also allows a lot of other BS (tracking scripts and such) which NoScript blocks.

    It'd be nice to see something more like uBlock, or maybe have uBlock extended to do this, where it also blocks all the tracking crap, autoplaying videos, etc., using a curated blacklist. There are some things out there like Ghostery, but they're not trustworthy since they're run or funded by the ad companies.

  11. Real Reason by ThatsNotPudding · · Score: 2

    Screen Door was already copyrighted.

  12. Re:Whacky Version Names by Voyager529 · · Score: 2

    Well, let's see. They used to have simple version numbers (Photoshop 5, Premiere 6.1, etc.). This got them into a bit of trouble because, for example, the upgrade from Premiere 6.1 to Premiere 6.5 was a paid upgrade, but since it wasn't a major change in the actual back end code, that was a bit messy. Additionally, Adobe wanted to focus more on the program bundles rather than the individual applications, and thus the "Creative Suite" moniker was born. Incidentally, this also helped deal with the psychological "high version numbers" issue (anyone want WinZip version 20?).
    Now, Adobe is betting the farm on everyone being okay with renting their software. Resultantly, they're trumpeting "All teh Updates!!!111", which they're hoping will make version numbers irrelevant - it's just "the most recent build we've rolled out the door". This ends up being a bit of a challenge because they also like doing Apple style keynotes, where they show all the CC subscribers how it's now possible to start editing videos on one's iPad and then continue on the editing bay. So, they thus distinguish the new feature sets that get introduced at the keynotes by the year of release of those features.
    Finally, Adobe's core applications aren't going anywhere - Photoshop, Indesign, Illustrator, Premiere, After Effects - none of them are going anywhere. In trying to make Adobe products more accessible to folks who don't have formal training in graphic/media design, things like Muse come into play...and since they're new products that don't have the long history, it makes sense to pick a name and branding that aligns with current trends. I'm sure that given the option, Adobe would rather have a list of edge case applications like Muse than to end up becoming known as a company like Oracle that continues to exist because support contracts. Adobe's also starting to see a handful of up-and-coming applications start to gain a certain amount of popularity. I don't care how much people like seeing the Photoshop splash screen, when Affinity Photo has 95% of the sophisticated functions of Photoshop, a similar UI, reads PSDs, and costs $50 one time, Adobe is going to take notice.

    Besides, software naming has seldom followed a true convention.

  13. Re:...would smell as shitty as any browser by PRMan · · Score: 2

    Privacy Badger is the closest that I have found to what you are asking. And it's curated by the EFF.

    --
    Peter predicted that you would "deliberately forget" creation 2000 years ago...