Now, they're going to continue working on Flash, but only on a new API that is implemented only in a single browser in Linux (and from statements from Apple and Mozilla, will stay that way), but keeping it compatible with the old NPAPI on Windows?
What I don't even....
Edit: Could it be that Google is planning to release (or has released) some Linux-based appliance where Flash support is a must?
Flash is appealing because it has features HTML/CSS/JS do not have and because everyone on every platform has it. Since mobile devices are becoming ever more important and Flash is not supported on those devices (or will not be) the second part of that sentence is no longer true.
Conclusion: Flash is dead. We will have to deal with it for years but it's on its way out. A web technology that will not work on mobile devices has no future.
Flash may well survive as AIR - that’s an uphill battle but it's possible – but that’s kinda irrelevant for the web.
If you were on Wikipedia you'd see a [Citation needed] here.
The real question is if this is true, why are they dropping flash for android?
“First, there’s Open… Rather than use Flash, Apple has adopted HTML5…” — and CSS3, SVG, and HTML5 have indeed provided most of the capabilities that once were Flash’s domain.
“Third, there’s reliability, security and performance.” — which is really three things, each of which Flash has an outstandingly poor track record with.
“Fourth, there’s battery life.”
“Fifth, there’s Touch. ¶ Flash was designed for PCs using mice, not for touch screens using fingers. For example, many Flash websites rely on ‘rollovers’…”
> Google declared Flash dead in Chrome for Android.
This is excellent news for web security. It will force other browsers to at least implement the Pepper API. Hopefully it will encourage them to use Native Client as well.
If you see the arguments against Native Client, it's also obvious using it to be able to keep supporting Flash would be rather...ironic.
You're saying Google is enforcing whatever it wishes upon others. Aka, non-standard stuff.
The Pepper API would be all nice if it wasn't hiding the NaCl vessel. NaCl is a very hard to standardize (yes, being open source has nothing to do with ease of implementation, or proper standards. News at 11.).
NaCl is also (one of) the vessel for Google to get more control over the web, due to the above, and that it can do stuff such as "take your C/C#/etc. app and run in it Chrome, via Chrome market!", while they know others can hardly ever implement it.
you can be relatively sure that Google pushed Adobe a little bit in that direction, and that eventually flash may be Pepper API only. Its easier for Adobe too.