Death of Flash

Out of context: Reply #176

  • Started
  • Last post
  • 205 Responses
  • 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

View thread