Re:Google moves to replace Flash with HTML5
by macspoofing on Friday May 20, 2016 @10:39AM
(#11738122)
What bugs me is that Google gave itself a pass by white-listing YouTube - because it turns out some people still need Flash on YouTube. Google should dog-food their own policies.
[ Parent
| on HN ]
Re:Google moves to replace Flash with HTML5
by IIlllIllIIIIlII on Friday May 20, 2016 @10:59AM
(#11738330)
Likewise, Google penalizes webpages by size. A 3 megabyte page gets a larger penalty than a 1 megabyte, which has a larger penalty than a 1 kB page.
But, they give themselves a free pass, as their own "webpage guidelines" page is 3.4 megabytes long! But, even worse, it has a video on a carousel that repeatedly downloads the video whenever it restarts the video loop.
Re:Google moves to replace Flash with HTML5
by josefresco on Friday May 20, 2016 @12:31PM
(#11739208)
How do you know they give their own web page a pass? It could be scored low and Google just doesn't care, or like all of us, has other priorities. The fact that Google recommends lightweight pages, and still builds heavy pages is contradicting, but doesn't mean they've built in some sort of "whitelist" for their own sites.
Re:Google moves to replace Flash with HTML5
by IIlllIllIIIIlII on Friday May 20, 2016 @12:39PM
(#11739285)
How about, "Google doesn't do what it makes others do"
which is true whether they give a boost to themselves or not.
Re:Google moves to replace Flash with HTML5
by Dylan16807 on Friday May 20, 2016 @12:54PM
(#11739407)
Google doesn't make websites be lightweight. Heavy websites get indexed just like any other. If they want to make a heavy page and accept the penalty, there's nothing wrong with that.
Are there parts of YouTube that require Flash in Chrome other than legacy embeds on non-YouTube sites that enable the embedding page to script the Flash embed via a JS API?
Re:Google moves to replace Flash with HTML5
by macspoofing on Friday May 20, 2016 @05:18PM
(#11741593)
>other than legacy embeds on non-YouTube sites that enable the embedding page to script the Flash embed via a JS API
That's probably it. Then again, it's not just Google that has to deal with legacy applications. So yeah, if you're going to shove this policy in the name of open standards, dog-food it and deal with the same pain countless of companies will have to.