My guess is this dev had to debug a reported issue “youtube is slow”, and after realizing it is difficult to patch (likely because of shitty code in edge), started pointing fingers. No. That is called a bug, plain and simple. Maybe try fixing your browser implementation so a single empty element doesn’t destroy video performance...
Edit with one more thought: I also feel youtube’s response in not removing the element seems completely justified. Youtube has features to implement and deadline to meet. Why should google have to throw dev resources at fixing problems stemming from microsoft’s bugs with no benefit to themselves? M$ should be the one footing that bill, again, by paying their own devs to fix problems of their own creation.
What incentive does Chromium/Google ever have to fix an issue that only affects Microsoft users or non-Chrome users?
I elaborated more here: https://news.ycombinator.com/item?id=18703568
But that's not enough, apparently, so it was also "when you browse with chrome or firefox, we give you notifications saying you are draining your battery faster and should move to edge"[1]. This predates the stuff talked about in this article.
That's also like the start of these tactics. I'm sure Google and Mozilla asked Microsoft to stop doing that, "to no avail". Meanwhile, the complaint here is basically "they made our annoying and stupid notification not true". Having dealt with these tactics repeatedly, i can't work up any indignation over this. The only one i feel even mildly sorry for is Mozilla.
[1] https://www.theverge.com/2016/8/3/12369326/microsoft-windows...
Edit: I'll expand. You work for a company the bundled Chrome as a default install with many other toolbars and utility programs. You sell a line of computing products where Chrome is not only the default, it is literally the only browser than can be installed. Chrome is the default browser on the world's most popular OS (Android). Multiple Google properties have refused to work on other browsers and displayed a popup asking people to switch the Chrome (Inbox is the one I remember most vividly). Here's a link to people trying to figure out how to get Chrome to stop asking to be default every time it opens: https://www.tenforums.com/browsers-email/59843-how-stop-goog... As you can see it's not exactly an easy task. All of this, and probably more, and you're here talking about what Windows does? C'mon man.
It's no different than any other form of bias, even if it seems more socially acceptable here.
If you want to argue with what I actually wrote, happy to have that discussion. Otherwise, not interested, sorry.
Beyond that: I've read every 'DannyBee comment on HN for the past several years and I assure you he has far stronger opinions about register allocators and the LLVM development process and open source licensing than he does about people criticizing Google.
I think you owe him an apology.
That comment would be equally as worthwhile and useful if you had started it with some other form of bias to justify it like "Wait, a woman who is black ...."
If your comment starts with some form of "well you are an x so ...", it's probably not actually addressing anything other than your own interesting biases against people.
Or you know, just dismiss whatever you want with bias and claims of whataboutism. I guess that works too!
Despite your claim of whataboutism, i'm instead showing the author is incredibly conveniently eliding large parts of actual history in trying to make their point. You may want to argue those shouldn't matter (or make it worse). That's at least a more valid argument than you made.
I would argue if you asked most people they do in fact matter because the world is not an abstract idealist paradise.
The internet definitely never has been in the past, so saying it isn't in the future is not particular interesting.
What? I am so lost. The complaint is that video acceleration is being disabled, perhaps intentionally, resulting in loss of battery life. That is a bad thing for users, regardless of this whataboutism nonsense. If there was some reason the empty tag was added, Google PR is free to let us know. The fact that they did not is quite telling.
How can you support something blatantly bad as this unless you work for that company? Oh wait...
And Chrome is full of dirty tricks of it's own. For example they paid Gigabyte to add Google Chrome to show up as an 'update' to system software.
http://puu.sh/CjVYU/804038501f.jpg
So lets stop this, which company is worse thing and work towards fixing bugs and making users happier.
I tend to agree with the point made in a different part of the thread that arguing against people based on the company they work for is not productive. People are more than just cogs in a machine and have a right to be regarded as such, even if it's just for the sake of argument.
The correct question for DannyBee might be How can you support something blatantly bad as this even if you work for that company?
I'm sure there are plenty of Googlers who would have a problem with deliberately adding a misfeature to a site to slow down a competitor's browser, plenty would fix a bug like that if it were reported and it was really just a bug, etc. Those guys aren't all in leadership positions...
Maybe you want to walk that statement back a bit? Wow.
This does not make the rule less dumb, but it is clear.
If you’re asking why they didn’t think to design the fast path to deal with Byzantine faults, it’s probably because why the hell should they?
Am I seriously underestimating the eng cost of such a patch, or is there some unwritten rule that browsers aren't supposed to mess with the HTML that a page serves?
Even though it's good for Microsoft resource and focus wise, it's bad for the consumer. Supporting Firefox will become more important, like back in early 2000s.
"A person claiming to be a former Edge developer has today described one such action. For no obvious reason, Google changed YouTube to add a hidden, empty HTML element that overlaid each video. This element disabled Edge's fastest, most efficient hardware accelerated video decoding. It hurt Edge's battery-life performance and took it below Chrome's. The change didn't improve Chrome's performance and didn't appear to serve any real purpose; it just hurt Edge, allowing Google to claim that Chrome's battery life was actually superior to Edge's. Microsoft asked Google if the company could remove the element, to no avail."