Announced last May
HTML5 by Default for Google Chrome
It comes into action with Google Chrome v55.0
(I mean seriously version 55, fifty five ? … )
and everyone see that as the death of Flash (again)
here some examples and comments.
Making true on its promise, Google now blocks Adobe Flash by default on its Chrome browser.
As part of Chrome 55, Adobe’s Flash will be replaced by HTML5.
haha “Adobe’s Flash will be replaced by HTML5” sounds like wishful thinking,
not very informed article (I guess the writer had no clues)
but here another quote from it
“This kind of Flash slows you down. HTML5 is much lighter and faster, and publishers are switching over to speed up page loading and save you more battery life. You’ll see an improvement in responsiveness and efficiency for many sites.”
Let me translate that for you:
Now that Google decided to not support Flash Ads anymore
then it is in all their interest to push harder for HTML5
the arguments (or excuses) are the same bullshit as usual: speed up page loading, battery life, etc.
I can guarantee you that you don’t need Flash to have slow website, I got a system with 64GB of RAM and Chrome is eating easily 20GB of RAM just to display HTML pages without Flash, and conveniently there is no more
about:memory to see the details.
Search the web for “Chrome” and “RAM” and you will see a huge amount of people complaining about Why Chrome Uses So Much Freaking RAM, to the point that you have a special entry in Chrome help named Reduce Chrome memory.
Flash is used as a scapegoat (since 2010).
Your web pages are slow? that’s Flash fault.
Site web are full of scam and insecure? that’s Flash fault.
Battery life running out? that’s Flash fault.
Well… it’s what Google want you to believe, I mean really? Google who pride themselves to only hire the smartest of the smartest, who dedicates horde of engineering power into their Chrome browser are defeated by what? a simple plugin.
Google’s long-promised farewell-to-Flash took another step last week , with the Chocolate Factory announcing it’s off-by-default for most users, in most cases.
From Chrome 55, Google’s browser will check sites to see if they support HTML5. If so, Chrome will
run the auto-play video adproceed to play video; if not, the user will be prompted to run Flash, if they want.
First, WTF with this title? the link read as “Google killing Flash slowly” … but the title sounds like a bad joke, I guess we can call that restrained irony ?
They must know they article is full of shit but they have no other choices to offer the clickbait as it works so well …
At least they list the 10 sites being “whitelisted”
and they point out
In fact, let’s go back to the intro of the article with that other little joke
run the auto-play video ad
it’s striked out but it is probably the true reason of this “let’s block Flash” move from Google
Have you not noticed what happened to the web lately?
Every single freaking video which are now played trough HTML5 now autoplay in your face,
I even encountered web sites where 3 or more videos all autoplay at the same time on the same page
That’s basically what Google is promoting with this “move”, they want to sell advertising, they want to be able to tell their customers “oh yeah your video ads will autoplay”
They secured this feature with HTML5.
My opinion is still the same, browsers still have to provide Flash because users want to consume Flash content on the web, this very same SWF content has not been replaced by HTML5.
It’s been 6+ years they keep repeating “Flash is dead”, that they wish HTML5 could replace it, but it seems the “old” Flash content are still not replaced while at the same time they are not that much “new” HTML5 content.
If users have seen that Chrome was eating their RAM I think users will also notice that Flash content is harder to access and I think they will complain about it.
One thing I know for sure is that browser hegemony is not guaranteed, Netscape was defeated by IE6 which was defeated by Firefox which then was defeated by now Chrome, but it can change again.
I would not be surprised to see a MS Edge browser coming to macOS and Linux (see Bringing ChakraCore to Linux and OS X), Microsoft already clearly went after Node.js (see Ommm… devs, align your Chakra, whispers Microsoft, you don’t need Google’s V8…) so yeah they could go after Chrome for the very same reasons.
When a user who really want to consume SWF content get pissed off by Chrome and he/she got a nice alternative with MS Edge, what do you think they gonna do? Switch browser.
Let me give one last example, remember about Youtube announcing how they switched from the Flash player as their default video player to HTML5?
some users did not like that and they wanted to continue to use Flash as their default video players,
and then those addon appeared in Firefox
- YouTube™ Switch to Flash® Player ~14K users
- YouTube™ Flash-HTML5 ~48K users
- YouTube Flash Video Player ~282K users
- YouTube Flash Player ~376K users
The last one mention this
Why you should try this add-on? Because for a lot of people the HTML5 player is laggy and consumes much more material resources (CPU, RAM) than Flash® Player. Once installed you have nothing to do and you can easily switch between both players if needed. Plus, this add-on also works for embedded YouTube™ videos, and if more than 300k people are using it it’s because it works for them! Give it a try!
That’s basically 500K+ users that tell Youtube and Firefox that they do not want HTML5 to play video.
And btw there is also the same kind of extensions for Chrome, see Flash® Player for YouTube™.
My point is that not all users necessarily accept the bullshit that the browser try to force upon them.