I am confused with this article. google does this with every browser not just edge.
Google Chrome's fear of Microsoft Edge is revealing its bad side
201–210 of 289 posts
Re: Google Chrome's fear of Microsoft Edge is revealing its bad side
#202FF f'd up when they banned Dissenter extension and with their welcome screen full of google tracking. Not to mention a ton of "metric" requests FF is doing in the background. As we've learnt, Chrome has a ton of google-specific code built into it(most notably the tracking id on youtube that was exposed few weeks ago) and a ton of background requests. MS Edge is not that different. Sure it is cleaner Chrome but MS is…
but they can't be ALL bad.
Re: Google Chrome's fear of Microsoft Edge is revealing its bad side
#203Earlier quoted context omitted.
Pretty interesting article. > "Google Chrome ads started appearing next to Firefox search terms. Gmail & [Google] Docs started to experience selective performance issues and bugs on Firefox. Demo sites would falsely block Firefox as 'incompatible'," he said. > "All of this is stuff you're allowed to do to compete, of course. But we were still a search partner, so we'd say 'hey what gives?' And every time, they'd say,…
> "When I started at Mozilla in 2007 there was no Google Chrome, and most folks we spoke with inside [Google] were Firefox fans," Nightingale recollected in a Twitter thread on Saturday. > "When Chrome launched... ... many of those same folks started to use Chrome, making it easier to miss Firefox bugs? Jonathan Nightingale is claiming a company-wide conspiracy ("coordinated plan" in Jonathan's words) across "hundred…
> We're talking Google here: they have a hard enough time coordinating internally when they're openly trying.
Yet for some reason each oops only resulted in Google's favor. It's like slipping on banana peel and doing a perfect backflip. Every time.
Re: Google Chrome's fear of Microsoft Edge is revealing its bad side
#204Earlier quoted context omitted.
It's an artifact of how they develop and test software. And ultimately Firefox suffered these bugs because their product wasn't compelling. Googlers push new code to production regularly, with the cycles getting faster all the time. It used to be biweekly (as the article alludes). Then it was weekly. Then it was daily. Then it was "push on every green build". If you push to production literally the moment your test s…
> They always got fixed quickly when reported. Having been involved in a number of these reports, this is flat-out false. Basic "fix your CSS to not rely on this Chrome bug; here's the exact diff you want to make it work both in browsers that follow the CSS spec and in Chrome" things regularly take 2-3 months to apply on the Google side. Basic "your browser user-agent sniffing is broken _again_ in the same way as thr…
The idea that google web apps are frequently released, and the fact that there is high latency between identification of a defect and it being fixed 100% in production, are not conflicting facts.
Disclosure: xoogler with my name carved in stone outside Mozilla HQ.
Re: Google Chrome's fear of Microsoft Edge is revealing its bad side
#205Earlier quoted context omitted.
Its still not great though :( (relatively speaking)
I had been a hardcore Chrome user since the comic book days and switched back to Firefox last year. Imported my passwords and bookmarks and the transition couldn't have been smoother. I still have Chrome installed but haven't opened it more than a handful of times since. What about your experience hasn't been great?
Mobile:
Too much.
Web:
- Syncing:
1. Very often hangs on "slow" networks. Syncs for minutes at a time and stops the browser from loading new pages (annoying)
2. Mangles bookmarks. Merges folders I don't want merged and adds bookmarks I've deleted before
- RAM creep
1. Memory leak? Firefox consistently takes up more and more memory the longer I use it
2. Poor suspend/dump functionality on Linux. If you have multiple tabs open, Firefox can quickly freeze your entire system (swap makes no difference). I have to use a 3rd party addon to have inactive tabs "suspended" so my system doesn't freeze
3. Unlike chrome, I don't think Firefox runs seperate processes for tabs. OOM killer never triggers.
- Slow
1. It's just slow. Even on a great laptop with a gigabit connection, it's slow.
- Long startup (self-explanatory)
Re: Google Chrome's fear of Microsoft Edge is revealing its bad side
#206Earlier quoted context omitted.
This is part of the reason I use Safari as my default browser
I hope this is a joke. Safari is easily the worst of the big four, and view web standards as suggestions that are to be ignored at any time. My company doesn't support IE anymore, but safari, not edge, is the new hated browser for web dev for sure.
Compared to what, Chrome? It took them how long to get position sticky, backdrop filters, etc? Meanwhile Google views web standards as their property they can willy-nilly do with what they please.
Re: Google Chrome's fear of Microsoft Edge is revealing its bad side
#207Earlier quoted context omitted.
I had been a hardcore Chrome user since the comic book days and switched back to Firefox last year. Imported my passwords and bookmarks and the transition couldn't have been smoother. I still have Chrome installed but haven't opened it more than a handful of times since. What about your experience hasn't been great?
Why do you choose to use the built-in web browser password manager?
Really convenient.
I use KeepPassXC, but Firefox PW is streamlined very well.
Re: Google Chrome's fear of Microsoft Edge is revealing its bad side
#208There are people using Microsoft Edge with Google Docs? What sort of logic puts one in this position?
Huh? Edge integrates better with Windows in various ways. So it makes sense to use Edge on Windows. Google Docs is one of many online office suites like Office 365. Google Docs came before Office 365 Web so people may already be used to that one. I fail to see the mental gymnastics necessary to have this all make sense.
Re: Google Chrome's fear of Microsoft Edge is revealing its bad side
#209Earlier quoted context omitted.
I hope this is a joke. Safari is easily the worst of the big four, and view web standards as suggestions that are to be ignored at any time. My company doesn't support IE anymore, but safari, not edge, is the new hated browser for web dev for sure.
Compared to what, Chrome? It took them how long to get position sticky, backdrop filters, etc? Meanwhile Google views web standards as their property they can willy-nilly do with what they please.
I’m still irritated that only Safari implements tail call elimination as specified in the ES6 spec.
Re: Google Chrome's fear of Microsoft Edge is revealing its bad side
#210Earlier quoted context omitted.
This is part of the reason I use Safari as my default browser
I hope this is a joke. Safari is easily the worst of the big four, and view web standards as suggestions that are to be ignored at any time. My company doesn't support IE anymore, but safari, not edge, is the new hated browser for web dev for sure.
Talking from the user perspective ?
The chrome/ram meme are enough to explain the issue
And I’m sure macbook owners care about battery more than what you think !
And for the argument of Safari is the hated browser I’m more than okey with that at least they still test for it (I feel sorry for Firefox because the oups we didn’t test blablabla