Flash vs HTML5 Debate: A Call for Sanity and Pragmatism
•Als PPT, PDF herunterladen•
0 gefällt mir•475 views
This document summarizes a talk about Flash and HTML5. It discusses the history of Flash and criticisms of it being a proprietary closed platform. It also talks about HTML5's capabilities and limitations compared to Flash. While HTML5 support across browsers is inconsistent, Flash still provides capabilities beyond what HTML5 can do effectively like DRM, webcam access, and advanced animation. Flash remains useful for building cross-platform applications, games, and visual prototyping, though tooling needs improvement. Both technologies have tradeoffs around openness, performance, and developer overhead.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (19)
Andere mochten auch
Andere mochten auch (8)
Ähnlich wie Flash vs HTML5 Debate: A Call for Sanity and Pragmatism
Ähnlich wie Flash vs HTML5 Debate: A Call for Sanity and Pragmatism (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Flash vs HTML5 Debate: A Call for Sanity and Pragmatism
- 1. Flash and HTML5 A call for sanity A talk by @andrewdotdobson Creative Class Meetup | 11th November 2012 | andrew dobson
- 2. Thoughts on Flash An exercise in FUD
- 3. FUD in action “Adobe’s Flash products are 100% proprietary. They are only available from Adobe, and Adobe has sole authority as to their future enhancement, pricing, etc. While Adobe’s Flash products are widely available, this does not mean they are open, since they are controlled entirely by Adobe and available only from Adobe. By almost any definition, Flash is a closed system.” Steve Jobs, 2010.
- 4. Is Apple committed to standards? Then why don’t they implement HTML5 video?
- 5. Product or platform? What actually is Flash?
- 6. Evolution of the web
- 7. Web platforms Application Code + Runtime Actionscript 3 and Flash/Air LAMP .NET HTML5 and the browser
- 8. Where Flash falls down Poor coding standards (GUI) Advertising Compatibility
- 9. Coding standards Knowing how to use CS5 != understanding a technology
- 10. Flash banner advertising Specifications still in AS2 AVM conflicts and performance drag. Pressure for reform required
- 11. Compatibility Should flash be on mobile?
- 13. Not everything needs to be mobile http://www.remembrance2012.co.uk/
- 14. It’s political He who controls the standard, controls the universe.
- 17. Setting expectations Clients and users do not care about technology
- 19. Whichever way you cut it Browser support is inconsistent
- 21. CSS3 Transitions support: Media Query support:
- 22. Hacks CSS Pie Modernizr Branched sites <!– [if IE] -->
- 23. Developer overhead Standards dev is more intensive Testing/QA Hacks and exceptions Sheer amount of typing
- 24. A simple logo animation http://codepen.io/andyunleashed/pen/jnpHc http://html.adobe.com http://g-plus-follow-me-animated-button.tumblr.com/animations-examples/ae-text-effect
- 25. Things that HTML5 cannot do (effectively) DRM Webcam Streaming Full screen Advanced audio/DSP Advanced animation Real-time 3D Consistent layouts, rich text and transitions
- 27. Flash use cases 1. Augmenting the browser 2. Extending beyond
- 28. Cross platform adaptive applications Single codebase, multiple deployments, smart assets – efficient, scaleable and rapidly developed. Quick porting of current web properties into native Rapid visual prototyping
- 29. Stage3D and Starling GPU access for gaming, mobile application development and rapid visual prototyping
- 32. Tooling Adobe’s developer tooling is largely poor Pros use: Flash Develop (PC), FDT Flex SDK includes Air – be wary of beta releases Debug tools: Monsterdebugger, Monacle (coming soon) Game dev studio Alchemy, native extentions Unity, Cadet3D, Prefab for 3d modelling and animation
- 33. Frameworks and open source Greensock – LoaderMax, TweenMax, Throwprops Starling and Foxhole for GPU 2D Away3D, Flare, Minko for Stage3D CasaLib – utilities Robotlegs, PureMVC, Gaia – Design pattern frameworks AS3NUI, In2AR, OpenCV – image processing and NUI Nape, Box2d – Physics OSMF, Tonfal, Stardust – media playback, audio, particles Minimalcomps – UI components Literally hundreds of great libs
- 34. Summing up What have we learnt?
- 35. NO IDEOLOGIES
Hinweis der Redaktion
- Brief introduction. Response to HTML5 talk by Tareq, with due respect. An increasingly anti-flash world, but there seems to be some confusion over what Flash actually is, and what it should be used for.
- In 2010, Steve Jobs published an open letter entitled ‘Thoughts on Flash’. In it he outlined his opinion on web standards etc. It is the document that effectively killed flash in the browser. FUD means Fear, Uncertainty and Doubt. It is a techique that Apple, and many other corporate entities use to seed unease in the consumer base. It’s worked spectacularly well, but when you strip it down in detail, it’s misleading at best.
- In 2010, Steve Jobs published an open letter entitled ‘Thoughts on Flash’. In it he outlined his opinion on web standards etc. It is the document that effectively killed flash in the browser. FUD means Fear, Uncertainty and Doubt. It is a techique that Apple, Adobe and many other corporate entities use to seed unease in the consumer base.
- Video evidence!
- So what actually is Flash, why is it dead or dying? Apple makes reference to it as a product – something which Adobe monetises and controls. In fact, the only thing which is monetised is the creation tooling, and, more recently, certain power tools (like alchemy) for high-end, monetised use cases. A stable runtime and an SDK for it is no different to the iOS SDK or Android SDK or any other Software Development platform currently around. Whether or not it’s ‘open’ is neither here nor there. It’s not supposed to be, and that’s what gives it strength.
- The biggest change to the browser landscape has been the speed of iteration on browser technology. This is what has helped establish web browsers.
- Every software base has a runtime. This can be the device OS or it can be another layer which interprets the code for the device it’s running on. Flash (specifically the AVM) is the runtime for swfs. So is AIR. Browsers are effectively a runtime for HTML, CSS and JS. There are big differences between compiled code and runtime code.
- There are places where Flash is falling down. The accessibility of the Adobe tooling means that it’s all too easy to write applications without understanding exactly what’s going on under the hood, and therefore being unable to optimise. Let’s take a closer look at each of these things.
- Every software base has a runtime. This can be the device OS or it can be another layer which interprets the code for the device it’s running on. Flash (specifically the AVM) is the runtime for swfs. So is AIR. Browsers are effictely a runtime for HTML, CSS and JS. There are big differences between compiled code and runtime code.
- Every software base has a runtime. This can be the device OS or it can be another layer which interprets the code for the device it’s running on. Flash (specifically the AVM) is the runtime for swfs. So is AIR. Browsers are effictely a runtime for HTML, CSS and JS. There are big differences between compiled code and runtime code.
- Every software base has a runtime. This can be the device OS or it can be another layer which interprets the code for the device it’s running on. Flash (specifically the AVM) is the runtime for swfs. So is AIR. Browsers are effictely a runtime for HTML, CSS and JS. There are big differences between compiled code and runtime code.
- But why should it? Black negative...etc.
- Every software base has a runtime. This can be the device OS or it can be another layer which interprets the code for the device it’s running on. Flash (specifically the AVM) is the runtime for swfs. So is AIR. Browsers are effictely a runtime for HTML, CSS and JS. There are big differences between compiled code and runtime code.
- Blacknegative – showcase HTML5 site.
- So let’s just look at four HTML5 and CSS3 technologies...
- Hacks exist and good use is made of them, but they are hacks. Any non-functional code which enters the program to force it to behave causes inherent instability within the system.
- So let’s just look at four HTML5 and CSS3 technologies...
- By effectively, I mean consistently across platforms without hacks, or with experimental builds etc.
- Cufon drawing into canvas fails AA
- Every software base has a runtime. This can be the device OS or it can be another layer which interprets the code for the device it’s running on. Flash (specifically the AVM) is the runtime for swfs. So is AIR. Browsers are effictely a runtime for HTML, CSS and JS. There are big differences between compiled code and runtime code.
- Every software base has a runtime. This can be the device OS or it can be another layer which interprets the code for the device it’s running on. Flash (specifically the AVM) is the runtime for swfs. So is AIR. Browsers are effictely a runtime for HTML, CSS and JS. There are big differences between compiled code and runtime code.
- Every software base has a runtime. This can be the device OS or it can be another layer which interprets the code for the device it’s running on. Flash (specifically the AVM) is the runtime for swfs. So is AIR. Browsers are effictely a runtime for HTML, CSS and JS. There are big differences between compiled code and runtime code.
- Every software base has a runtime. This can be the device OS or it can be another layer which interprets the code for the device it’s running on. Flash (specifically the AVM) is the runtime for swfs. So is AIR. Browsers are effictely a runtime for HTML, CSS and JS. There are big differences between compiled code and runtime code.
- Every software base has a runtime. This can be the device OS or it can be another layer which interprets the code for the device it’s running on. Flash (specifically the AVM) is the runtime for swfs. So is AIR. Browsers are effictely a runtime for HTML, CSS and JS. There are big differences between compiled code and runtime code.