The best way for Adobe to save Flash is by killing it
1–10 of 43 posts
Re: The best way for Adobe to save Flash is by killing it
#2HTML5 is not a valid alternative to Flash. Sure, there is some overlap between them, but there are way more differences.
It's (like so much else) like comparing an apple to an orange.
Re: The best way for Adobe to save Flash is by killing it
#3HTML5 is not a valid alternative to Flash. Sure, there is some overlap between them, but there are way more differences. It's (like so much else) like comparing an apple to an orange.
The implementations may differ, but the main use-cases are the same. So it's like comparing an apple to an orange when you want to choose a healthy supplement to your diet ;)
Re: The best way for Adobe to save Flash is by killing it
#4So instead of adobe being the monopolistic developer of tools for the successful flash platform , adobe should compete with everybody else on developing tools to html5?
This doesn't seem like a great business move, at least not before they tried everything they can to keep flash important.
Re: The best way for Adobe to save Flash is by killing it
#5Eh.
The best way for Adobe to save it is to open source the plugin though I suspect the resulting fragmentation would be a hindrance as well. A certification process of some kind might be helpful in that regard though.
I'm sure there are patent and licensing issues getting in the way of such a move.
Re: The best way for Adobe to save Flash is by killing it
#6The reason that the Flash authoring tools work in a sane manner is because there is a single, consistent runtime that they target.
There is a vast graveyard of tools that tried to wrap html and javascript so you could make reasonable GUI authoring tools. To my knowledge they were all plagued by consistency and performance problems, or placed severe limits on what you could author.
This is less of a way forward than it is a pipe dream, no matter how promising Canvas looks.
Re: The best way for Adobe to save Flash is by killing it
#7So instead of adobe being the monopolistic developer of tools for the successful flash platform , adobe should compete with everybody else on developing tools to html5? This doesn't seem like a great business move, at least not before they tried everything they can to keep flash important.
But isn't ActionScript completely open? And the flash framework is open too. You don't need Flash CS4 to use flash. You can also program it with a third party IDE and then use the free compiler. This would be quite comparable.
Re: The best way for Adobe to save Flash is by killing it
#8The reason that the Flash authoring tools work in a sane manner is because there is a single, consistent runtime that they target. There is a vast graveyard of tools that tried to wrap html and javascript so you could make reasonable GUI authoring tools. To my knowledge they were all plagued by consistency and performance problems, or placed severe limits on what you could author. This is less of a way forward than i…
Yes the existing tools are pretty awful... but they're generally made by small companies that don't know how to build tools, building on the current implementations of HTML, CSS, and Javascript. Has anyone given it a real shot, targeting the newest features of HTML5?
Adobe on the other hand has built industry standard tools over and over again (Photoshop, Illustrator, etc). They've proven that they can export their apps to other platforms (iPhone). What they're not so good at is building open browser runtimes...
Re: The best way for Adobe to save Flash is by killing it
#9[deleted]
Re: The best way for Adobe to save Flash is by killing it
#10HTML5 is not a valid alternative to Flash. Sure, there is some overlap between them, but there are way more differences. It's (like so much else) like comparing an apple to an orange.
The implementations may differ, but the main use-cases are the same. So it's like comparing an apple to an orange when you want to choose a healthy supplement to your diet ;)
The anti-Flash crowd with their fantasy about how HTML5 >= Flash are missing one phenomenally tragic detail ...
We're going to have HTML5 for the next twenty years - and right now it's only a sometimes substitute for Flash. If you think HTML5 is going to meet your requirements for the next 20 or more years.. well, assuming you're pushing 30 like me we're actually going to be close to retirement age by the time HTML5 is fully replaced by it's successor.
Arguing Adobe should kill Flash for HTML5 is the same as arguing the W3 should kill HTML5 for HTML 2.0 - it's 15 years old, how's it stack up against your requirements today?
Technology has never stood still for the W3C and market penetration to catch up, and 'kill flash' is betting that this time it will ... silly.