23 ms·

Lots of us do. Firefox is my browser on all my devices. I do use Chrome when visiting Google Docs which I assume is deliberately sabotaged on Firefox though.

SafaT 6y ago
I strongly agree with you, most of the time I feel that non-Google browsers including Safari is somehow blocked or slowed down.
- shadowgovt 6y ago
  It's more lack of optimization. We could alternatively put the blame on Mozilla's doorstep for not optimizing FF's engine to run Docs better.
lettergram 6y ago
I found Firefox to work fine on google docs tbh. It used to be slower, but haven’t had an issue in probably a year
- vishnumohandas 6y ago
  On my 2015 Mac, both Docs and Maps perform significantly better on Chrome, and I keep it around for these 2 use cases.
- tedivm 6y ago
  It really depends on which part of google docs you're using. Trying to use the presentation system with Firefox is an awful experience for example.
subhro 6y ago
I have never used Chrome and use Safari with GDocs. It seems fairly functional to me. What is the sabotage scene you are talking about?
- Sebastian_09 6y ago
  I have a different experience with that: on a current MBP, Google office suite software (docs, slides, agenda, mail etc) regularly uses 100% cpu in safari for no apparent reason, and clearly also has some memory leaks were single tabs bloat to 2-3 gig memory... Have to kill the the threads manually. I would say it’s fairly unoptimized / pushes you to chrome
- reachtarunhere 6y ago
  I second the experience of the other commenters. Keep it open long enough and it sucks up all the resources in non-chrome browsers. I also include Google Slides in my experience btw. It is more severe with Slides than docs.
shadowgovt 6y ago
It's not deliberate; it's lack of investment. Docs is complicated enough that the small deviations in browser implementation add up---to make something as complex as Docs not work in Firefox, all you have to do is be willing to publish without hating new features on FF end-to-end tests.
methodsignature 6y ago
Might just be that Google doesn't test on Firefox and also maybe are "to smart for their own good" coming up with out of the box solutions that can be more likely to fail to begin with. Maybe I'm being overly optimistic, but I kinda read myself as saying "they probably just don't give a sh!+."

SafaT 6y ago

I strongly agree with you, most of the time I feel that non-Google browsers including Safari is somehow blocked or slowed down.

shadowgovt 6y ago
It's more lack of optimization. We could alternatively put the blame on Mozilla's doorstep for not optimizing FF's engine to run Docs better.

lettergram 6y ago

I found Firefox to work fine on google docs tbh. It used to be slower, but haven’t had an issue in probably a year

vishnumohandas 6y ago
On my 2015 Mac, both Docs and Maps perform significantly better on Chrome, and I keep it around for these 2 use cases.
tedivm 6y ago
It really depends on which part of google docs you're using. Trying to use the presentation system with Firefox is an awful experience for example.

subhro 6y ago

I have never used Chrome and use Safari with GDocs. It seems fairly functional to me. What is the sabotage scene you are talking about?

Sebastian_09 6y ago
I have a different experience with that: on a current MBP, Google office suite software (docs, slides, agenda, mail etc) regularly uses 100% cpu in safari for no apparent reason, and clearly also has some memory leaks were single tabs bloat to 2-3 gig memory... Have to kill the the threads manually. I would say it’s fairly unoptimized / pushes you to chrome
reachtarunhere 6y ago
I second the experience of the other commenters. Keep it open long enough and it sucks up all the resources in non-chrome browsers. I also include Google Slides in my experience btw. It is more severe with Slides than docs.

shadowgovt 6y ago

It's not deliberate; it's lack of investment. Docs is complicated enough that the small deviations in browser implementation add up---to make something as complex as Docs not work in Firefox, all you have to do is be willing to publish without hating new features on FF end-to-end tests.

methodsignature 6y ago

Might just be that Google doesn't test on Firefox and also maybe are "to smart for their own good" coming up with out of the box solutions that can be more likely to fail to begin with. Maybe I'm being overly optimistic, but I kinda read myself as saying "they probably just don't give a sh!+."