3 ms·
Flash is a bad deal technically. It is the most straightforward solution for the kind of things you describe which cements its place for a while just by itself,
by cookiecaper 17y ago
Flash is a bad deal technically. It is the most straightforward solution for the kind of things you describe which cements its place for a while just by itself, but you should see some reasons for it to die.
It's a proprietary blob that Adobe controls. They can and have dropped support for non-conventional platforms in the past. You can't see what the Flash Player is doing. Adobe can at their leisure impose any kind of crazy restrictions on Flash content (because they control the Flash Player, which is required to watch Flash content, and its terms of distribution).
Flash is an ugly marr upon the otherwise open standards needed for a rich web experience, because its fate is completely controlled by Adobe's interests. Adobe has far too much ownership for the kind of reach Flash has, it is dangerous and should depart.
Flash Player itself is a behemoth and a hog. It spins up CPUs to full power without any need and in so doing causes heating issues, battery-life issues, and other bad things. It is inefficient and sad and not good. You should hope it dies so that you can actually watch full-screen video on non-Windows or non-x86 platforms at more than 15 FPS.
Flash is not like After Effects; AE sits on one side of the production process and its results play on regular cinema projectors, DVDs, and many other formats, including open, non-proprietary formats (anything that can save and playback video, including hard disks).
When you make something in Flash, you impose Flash Player upon all of its potential consumers (ignoring Gnash and others because they can't play very much). They have no choice but to allow the non-free Adobe blob on their machine if they want to consume your content. This is bad.
Flash is bad all around in the long-term. It's a convenient tool for designers to get the effects clients want, which is why it pervades so deeply, and I agree that Flash will stay in the game until a better tool emerges (HTML5 advocates, this means you should be working on an HTML5 IDE that will replace the Flash IDE and provide an easy transition path for current Flash users), but Flash is not a good thing. It needs to die.
- wallflower 17y ago> It's a proprietary blob that Adobe controls. Check out a recent hot topic from the Adobe Flex mailing list. Basically the Adobe Lawyers rewrote the license agreement for Flex (Flex being Flash that uses an integration server) - it now disallows trying to make any server of your own that talks the same language their now very $$$ (no single CPU option) integration server does. "took a look at the FB4 Beta 2 License Agreement, and here's what I found: 2.4.7 Flash (R) Builder(R) with LiveCycle(R) Data Services(LCDS) Data Management Library. Your rights to this Software are limited. In order to (a) utilize the file called "fds.swc" (the "LCDS Library") to develop associations , (b) utilize the LCDS Library to develop offline capability, (c) use the application modeling plug-in, or (d) utilize the LCDS Library to develop a product that competes with LiveCycle Data Services or BlazeDS, you must obtain additional licensing rights from Adobe."
- cnunciato 17y agoThat's because LCDS is a commercial product. Flex itself is not (it's an open-source framework), nor is Flex simply "Flash that uses an integration server."
- wallflower 17y ago> (d) utilize the LCDS Library to develop a product that competes with LiveCycle Data Services or BlazeDS BlazeDS is their open-source version. So they are saying you cannot compete with our open-source version, either. Yes, I know Flex is not just Flash. A haiku I wrote while waiting for mxmlc: it's more than just flash enterprise level big apps not just eye candy