Gregory's Server@iliazeus I can see the time it takes to initialize code _every time you scroll past it_ with my naked eye. That’s definitely a sign of a computer doing crazy amount of work
|
5 comments
 @iliazeus Yes, that’s the one from the post about JS bloat Anyways, if Google can’t reduce their embed down from 3 MB (while other people can) and also recommend to use 3rd-party embeds, I don’t trust them no to waste CPU, too  @nikitonsky can you please at least add links to YouTube videos? As I wrote in a neighboring thread, the <video>s are way too big to comfortably watch on a phone, or with a less-than-ideal connection. And hard to skim through to find a part I'm interested in, because of lack of chapters or a transcript. (as it turns out, _some_ of the things a YouTube embed does are actually useful, after all :) @nikitonsky thank you Sorry if my comments came of as too aggressive btw, I didn't mean that. Still having some difficulty expressing my thoughts correctly, especially in English. |
@nikitonsky that's a completely different website
Again, I was talking specifically about YouTube embeds, and how simply changing them all to <video> elements might not reduce the computer's work by that much, while introducing other complications and edge cases along the way.