Slashdot Mirror
The Future of Flash
An anonymous reader writes "Adobe is celebrating the 10th anniversary of Flash, and News.com has an article looking at the company's plans for the future of the technology. No longer just a choice for 'innovative' web designers, Adobe is positioning Flash as an application development platform, with special emphasis on video delivery and mobile device applications." From the article: "On Tuesday, the company intends to launch a microsite showing the evolution of Flash over the past 10 years, including video interviews with developers. Those videos will no doubt be played with the Flash Video Player, something many high-profile Web sites, including YouTube, have chosen to use as well. The success of Flash in the next 10 years rides largely on whether leading-edge customers like YouTube will design their Web sites with Flash, Lynch said. Adobe, which gained the Flash technology when it bought Macromedia, is trying to build an 'ecosystem' of developers and partners, he said. "
... "just say no".
Well, since I am on Linux and a 64 bit variant, I guess it will be another 10 years when I get to see the presentation.
[RIAA] says its concern is artists. That's true, in just the sense that a cattle rancher is concerned about its cattle.
i booed on them right on that article
but ya flash blows
they have terrible or no support for most architectures/OSes out there
and for a 'web application' platform thats just flat out unacceptable
they did release a 32bit only version 7 for linux, but there have been what? 2 other versions and a 3rd coming since then? and none of them work on linux..
also they dont have 64bit support
and as far as i know it ONLY works on x86
so if you write your interactive web application using ajax then it works on nearly every operating system known to man.. or flash and it works only on one
I've been doing Flash/AS professionally since the 5.0 days. The plattform has come a long way. For one, it actually has become a plattform, and not just some crappy IDE with a little scripting bolted on. Allthough not percieved as such, it's even closer to open source right now than Java. AS 2&3, MTASC, osflash.org and the GNU Gnash project continue to add OSS credibility and non-slashdot-bullshitting awareness in the developer community. I didn't like the hickup in the release line of the official Linux Flash Player though. If Flash won't reliably support Linux, it's a no-go for me and quite a few other serious Flash developers. The dev-laps of Macromedia where a nice place to get that straight to the devteam of flash and they got the message.
All in all it's clear that if Adope doesn't screw around to much they can't do much wrong. It's still the most widespread plattform ever with nearly zero-fuss cross plattform deployment via the web. You get a high profile independant VM, with a security model and security policy that remains unmatched in RIAs. And a rock-solid ECMA compliant OOP language along with it.
Ajax just isn't in that league. Nice for the one or other drag-and-drop gadget or small-scale data sync but that's about it.
XUL maybe will get there someday, if they get their stuff sorted out and manage to build a hassle-free XUL-Runner plugin for all major browsers. But I don't see that happening anytime soon.
We suffer more in our imagination than in reality. - Seneca
As someone coding an large scale application (hint, its part of a project that is costing billions of £) that is using Flex for the presentation layer (or presentation layer + as it is turning out to be), I have to disagree.
Flex (or Flash) is an API and can be made to develop complex applications. Though the question of "complex" is debatable. I think 10s of thousands of concurrent users with 10s of millions of daily transactions will be complex enough.
I've yet to see the Ajax app that performs to a high degree of accuracy to the same extent.
Server side execution of certain things? Sure, how do you want to go about it? RPC, WS, HTTP? These are obviously all wierd Adobe programming techniques that aren't used by millions of people across the planet. We're linked upto massive multiple clusters all running various Java servlets to perform all our server side needs, such as, for example working with that massive centralised DB.
Try looking at it from a security point of view as well. Flash is prone to fewer attacks. It is much harder to spoof a Flash application, you can't simply through up a look-a-like page, you can't use simple cross site scripting attacks, no SQL injection, simply fewer common techniques will stime it.
HTML is no greater universal than Flash, Flash has different players (which can be compensated for by directing the user to get the latest), HTML has all its IE/Firefox/Opera/etc problems.
In the end, Flash CAN be annoying, if simply used to create an annoying moving image... much like a gif can be annoying if used to create an annoying moving image, but it IS powerful and will only get more so.
As more features get added in Flash, there will be more vectors that can be used to potentially infest computers with malicious software. As it is, using Flash as an application development platform is a bad idea because nobody tends to program for security, and decides on programming for performance for media players, webcam broadcasts, video streaming, etc. As more code gets added on, holes will open up, eventually. As is the future of any piece of software - there will be a crack, hack, hole, exploit, whatever for it.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
As an application development platform? Sure, why not. As a web application development platform? No chance.
The fundamental problem with Flash is the same as it ever was. You have a presentation format that wraps up presentation, scripting and content into one binary bundle that couples everything together so tightly it's impossible to decompose. You might as well stick a Powerpoint presentation on the web. Virtually all of Flash's other problems that people complain about are merely symptoms of this one underlying design flaw.
With a normal web application, you can do all kinds of things with the various pieces. On a slow connection? Turn off the graphics. Indexing content? Just parse the HTML. Security worries? Switch off scripting. Hate the design? Use a user stylesheet. Missing a feature? Add it with Greasemonkey. Concerned with a particular part of the web application? Link directly to it.
Flash either makes these things impossible or way more difficult than they should be because everything is tightly coupled instead of loosely coupled the way all the other web technologies are. By itself, this single factor limits interoperability, which is the whole basis for the WWW's strength. Sure, you might be able to produce a fancy interface, but you're doing it at the expense of cutting off ties to the rest of the web's technologies. It's Flash's fundamental design flaw that Adobe/Macromedia don't seem to understand or care about fixing.
Ajax, on the other hand, works with all the other WWW technologies. It doesn't invent its own way of representing content, it uses HTML. It doesn't have its own layout system, it uses CSS. Its constituent components already all exist, and, more importantly, lots of other software is built to manipulate them.
For example, if I have my browser set up to automatically make tables sortable, this works with tables in an Ajax application because Ajax applications would just use a normal, standard HTML table. The same thing hasn't got a chance of working in Flash because it doesn't build on top of existing technologies, it throws them all away and does its own thing.
Flash isn't a way of creating web applications. It's a way of creating traditional applications and making them appear in a browser window. If that's what you want, then fine, go ahead and do that. But don't pretend they are web applications, because they've thrown away everything that makes the web so powerful and replaced it with something else.
Bogtha Bogtha Bogtha