Death of Flash

  • Started
  • Last post
  • 205 Responses
  • prophetone0

    Was on an IAB dev webinar call the other day and the push now is all HTML5 for online ad units. They even explained with infografi-radical slides how Flash is basically dead, time to let it go, etc.

    Their newly-released ad spec docs for 2015 are a clear shot across the bow for swf-lovers. HTML5 everywhere with a scaled sizing approach; HD mobile units; responsive ads TBD.

    Mobile device dominance is the nail in the coffin for Flash - and as more devs use HTML5 apps like Google Web Designer as the default go-to builder, which is free.

    To the future!

  • twokids0

    we just used flash to create interactive ui motion for user testing. helped dev out of a jam - we looked like heroes.

  • pinkfloyd0

    Anyone use Flash CC for exporting as HTML5?

    • I have tried it - fine for basic animation but scripting doesn't translate.fadein11
    • Its horrible.err
  • nb0

    I really want designers to keep using Flash as long as possible for web ads. I hope they keep pushing it.

    It's the next best thing to Ad-Block for iPhone.

  • err1

    We have to remember the best thing about flash was compression. All the HTML5 projects I've worked on were all bloated to hell.

    Google webdesigner is great an all. But it still produces projects that weigh 500% bigger than what I can do in flash in half the time.

    Let's not forget HTML5 is annoying when it comes to browser support.

    I think adobe should have taken out half the functionality of flash and made the plugin run as fast and clean as possible to become the new gif or something.

    • I agree with your last statement. Adobe had a responsibility to make Flash more mobile friendly.monospaced
    • But the designer can do that by being a designer and just not adding too much.CyBrainX
  • SteveJobs1

    I do think Jobs killed flash, but only as the final nail in the coffin as illustrated above. And not directly, mind you, and certainly not all by himself.

    Adobe didn't do their due diligence with the technology either. They jumped from a simple UI and a reasonably understandable (for most) AS 2.0 to the world of OO and they gave novice developers (and let's face it, this is the core of who was developing flash apps) too much rope to hang themselves with. These so-called developers knew nothing of garbage collection or memory management or using patterns for designing applications to run efficiently and thus you had flash applications that had the simple job of displaying a banner ad that would single-handedly take down a browser.

    As a result, the non-tech world and even the somewhat tech savvy that 'knew a little php - or whatever' but have never done any real program whole-heartedly bought into the notion, while firmly grasping their Steve Jobs prayer beads, that flash itself was to blame and that it was an outdated, inferior technology. With the propogation of this notion that flash sucked as a technology the bandwagoners (and i'm pointing at most of you) brought this browser technology to a screeching halt.

    In the early two thousands I might have cared as I appreciated and supported what the technology was and what it could do. Today I'm far removed from the tedium of typical web development and could mostly care less... ...except, I really did enjoy the rare creativity that the few, who knew, could squeeze out of it and bring us something purely enjoyable. But hey.. web standards and all that... flash is nonsense and the Web is serious business! Out with the old and in with the new!

    • Your point about Adobe is right but I think you're underestimating how much Steve Jobs had to do with it. No one was talking like him at the time.CyBrainX
    • He had the power to allow or not to allow Flash on iOS.CyBrainX
  • formed0

    Adobe was caught sleeping, no doubt. Jobs took the chance to not only kill a competitor, but to solidify Apple's profits via apps. Brilliant business move, imho, but he did kill an industry and send well paid programmers to the streets.

    I still care because much of what I do benefits from Flash (still used on large touchscreens, which now is a headache to keep things coordinated, before you could use literally the same file).

    I am fine with the way it is today - boring and predictable. All about money, money, money. Flash would have evolved in the same way, eventually - cleaner, more minimal, mobile friendly, etc. Just look at how long its taken this HTML5 to really work and it is still ages from the flexibility Flash had.

    • Sounds like your problem is really with Adobe for not letting it evolve?monospaced
    • Nope, it's with Jobs killing it, Adobe wasn't given a chanceformed
    • Agreed. And bash Flash all you want, what was the better alternative? No answer then and not ever 5 years later.CyBrainX
    • Since Jobs didn't work at Adobe, I find it hard how he could personally "kill" Flash. I mean, it's still around.monospaced
  • cannonball19780

    ^

    "Brilliant business move, imho, but he did kill an industry and send well paid programmers to the streets."

    That coasts on the whole "create jobs" as a goal fuzzy argument.

    • I'm positive there's a coherent english sentence in there somewhere. I've just yet to find it!SteveJobs
    • ;)SteveJobs
  • Beeswax0

    No matter what, i realy enjoyed making things on flash. Websites, animations, presentations. I was utilizing it with After Effects a lot. Tehy killed flash they killed my joy.

  • pinkfloyd0

    Bring back Director and lingo

  • raf3

    Here we paste again, just because people have short memory and only remember what they want to. Written almost 2 years ago by yours truly, slightly updated:

    --

    Let’s get the history right before nobody remembers anymore how it actually went.

    Not running on mobile did not kill Flash, neither did Steve Jobs. When iPhone came about, Flash had already been in agony, kept alive by its usefulness as a video player. People don’t remember this now, but by 2006 discussions whether or not Flash was “still ok” were commonplace here. Flash-only websites were already a big no-no, it was only ok to use “flash elements” on a page.

    In 2007, when iPhone arrived, I worked as a front-end developer and hadn’t opened Flash in months. And I loved Flash.

    Why was it dying, if it was (possibly still is) the better technology?

    It never fully integrated with the browser and never stopped being a foreign body in it. Never properly spoke with JS, kept breaking history, didn’t deep-link, had weird right-click menu and always opened a new window instead of a new tab. It was processor-heavy. It still spins the fans in my laptop and shrinks its battery time today to the point that I sometimes use a Flash-disabling plugin when on battery just to save power.

    One terminal flaw that was obvious by then was that it was never going to work well with Google indexing. This alone is enough to mean a death sentence to any web technology today.

    Add CSS Nazis who loomed over the internet at the time (Respect The Standards!), and a general distrust towards letting a single company control so much of the web to the equation (it wasn’t baseless, by then Adobe had proven more ‘evil’ than Google and Apple together), and you get the picture.

    Another, and when I think of it, possibly main reason of Flash’s demise was that Adobe was so busy appealing to programmers and making Air the next Java, that they completely neglected the crowd who made Flash as big as it was: designers.

    Neglected? They just showed them the finger, because the future and the real money supposedly was in the Air — Adobe's platform that was going to bring universal apps running both on Windows and OSX. Most good Flash designers I know had a hard time transitioning to AS 2.0 and never picked up on AS 3.0 when Adobe forced it on them. Many of them never bothered to.

    TL;DR: Jobs didn’t kill Flash, he only smelled its stench noticing before anyone else that Adobe already drove it into the ground.

    • Exactly. The short and sweet of all of it is, it's a plugin not a standard.prophetone
    • well saidhotroddy
    • The only point I agree with is Google. It being a standalone plugin is what made it work. HTML5 is still a long way from that reliability.formed
    • No one I knew was "smelling the stench", they were pushing for better sites and it was 3.0. We are still years behind.formed
    • so truemonospaced
  • i_monk1

    Get your shit together Adobe.

  • e-pill3

    my site i built in flash and forever IT STAYS™

  • i_monk0

    Firefox now blocks Flash by default

    http://gizmodo.com/firefox-now-b…

    I can't say I'm surprised. I've been prompted to upgrade Flash three times in the last week.

  • trooperbill-4

    2advanced and thedesignersrepublic now unusable... any think of any more? i wanna create a blog piece naming and shaming lol

    thanks

    • It'd be a lot easier to showcase how HTML5 is still years away from what was promised (if ever)formed
  • vaxorcist0

    yes, been dead for a while, but the nails in coffin for me were:

    1. no "back button" unless you code it, or (later) use a library, so we ended up re-inventing the browser not so well.... with lots of wasted time, as flash isn't about the page metaphor, but users kept demanding a back button

    2. action-scrapped... 2.0 code useless in 3.0, etc... and the "hand off" from another developer meant that a few weeks were spent figuring out how they did things before you started anything new....

    3. slow/fast... not as responsive as I'd like, depending on speed of network more than I'd like....

    4. XML parsing was cool, but so many exceptions and oddities that we had to write a ton of filtering scripts to fix stuff coming from a CMS to the XML file that flash apps were supposed to read in and would choke on all sorts of random things that other XML parsers would not choke on...

    • this.Krassy
    • 5. Slows and crashes browsers.inteliboy
    • yes, it does slow & crash browsers sometimes... is it bad code, or flash itself? or the network that a flash app is waiting on leaking memory while waitingvaxorcist
  • jaylarson0

    chrome seems to be freaking out today with it on as well. many unresponsive pages.

    • yup, same here.Krassy
    • smc fan control is helping a bunch.jaylarson
    • maybe not. i wonder it its pages that have flash. it's really weird.jaylarson
  • err-1

    Chrome is the new flash.

    jokes.

  • CyBrainX1

    Anyone using Celtra for ads? I will probably have to learn this for a freelance gig next month.

    http://www.celtra.com/

    • Meh its the same as all the other web interface html5 ad creators. It feels like free software that came with a pc in the 90s.err
  • instrmntl0

    Adobe Flash just took another step towards death, thanks to Google

    Google officially killed Flash advertising in its browser. As of September 1, any advertising that uses the technology requires the user to click it to play — it’ll otherwise remain frozen.

    http://thenextweb.com/apps/2015/…

    • Note: The writer seems a bit biased and probably doesn't know much about flash. That being said, its still a huge blow to Flash.instrmntl
    • Bullshit. You know Jobs killed flash all by himself.monospaced
    • Yup. He did. One of his smartest business moves. How much has that app store made Apple?formed
    • ^ and there's the biggest truth of all about Apple regarding Flash.CyBrainX
    • I was being sarcastic. Also nobody stopped anyone from making badass flash games for other smartphones but that never happened.monospaced