4 ms·

Likewise, but I've found the performance on a few key websites to be awful. Namely Facebook, and often Google Inbox. Another consequence of switching has been

Likewise, but I've found the performance on a few key websites to be awful. Namely Facebook, and often Google Inbox. Another consequence of switching has been difficulty in using things like my Apple TV or Chromecast (e.g. casting a video to my TV), or using my Mac's media keys to control Google Play Music.

throwaway181986 9y ago
Agree: I have similar performance issues with Google Inbox. E.g. I'm unable to attach files sometimes, and the interface is terrible. Still, I've switched to the new FF as my browser of choice and with the exception of those few sites it's great
albertgoeswoof 9y ago
Google inbox is terrible on ff, this is vendor lock-in by google, the new MS
- hutzlibu 9y ago
  Any proof of that claim? (that it is intentional from google and not just a ff issue?)
  - kuschku 9y ago
    Google didn't even make Inbox available on Firefox for months because they didn't care, and when they did, they ended up serving entirely different HTML and JS to FF. This is the same Google that is still keeping Allo Web and Google Earth a Chrome exclusive, the same one that has paid adware vendors to sneakily install Chrome, etc. Sure, you can believe that this is jist a coincidence. But that's one unlucky streak of coincidences. In fact, you'd be more likely to win the Powerball ten times in a row than for all this to happen by coincidence.
    - what_ever 9y ago
      Allo web has been available on browsers other than Chrome for a while - http://www.androidpolice.com/2017/10/03/allo-web-adds-support-firefox-opera-ios/ http://www.androidpolice.com/2017/10/03/allo-web-adds-suppor... This gives a good reason why Google Earth is only on Chrome - https://www.reddit.com/r/linux/comments/66ao68/new_version_of_google_earth_runs_on_chrome_only/dghvg1p/ https://www.reddit.com/r/linux/comments/66ao68/new_version_o... Disclaimer: I work at Google but not any of the related teams. I was curious myself about these so I Googled and came across the above two articles so these opinions are of my own.
      - robin_reala 9y ago
        Any chance you could poke the Hangouts team to get that working in Firefox? At this point they’ve have 28 months public notice that Mozilla would be deprecating NPAPI.
        gsnedders 9y ago
        Hangouts works in Firefox Nightly now.
        robin_reala 9y ago
        Oh! Great news, it didn’t when I last tested a couple of weeks ago so I’d assumed there was no progress.
- untog 9y ago
  Not really, it works fine on Safari.
  - kbenson 9y ago
    Which shared a lot of roots with Chrome. It's probably that they are optimizing for things that are fast in Chrome's JavaScript engine, which isn't necessarily what's fast in Firefox's Javascript engine.
    - lod723 9y ago
      Safari's JS engine is different than Chrome's though, no?
      - kbenson 9y ago
        Yes, although I'm not sure (and can't find god info on) whether they started from a similar lineage, or even if they just happen to just share some similarities that Mozilla's doesn't. If SquirrelFish (which became Nitro) happened to start with a similar architectural base, that could predispose them to make similar choices over time (e.g. if arrays are extremely efficient because the underlying types are well implemented, that could have survived and influenced later decisions. Array performance regressions might be seen as bugs that stop progress, and would possible cut of possible avenues of advancement). There's a decade of history in these engines with a lot of man hours put into them, and they were actively competing with each other very loudly for a while. There's little you could tell me I couldn't find some possible narrative justification for if I consider the PR, bureaucracy, talent and design decisions that might stem from those over a decade.
        gsnedders 9y ago
        V8 and JavaScriptCore were written entirely independently; there was little influence between the two. V8 started as an empty codebase, not a fork of JSC.
- notatoad 9y ago
  Google Inbox is also pretty terrible on chrome for me, i'm not sure i'd blame vendor lock-in.
  - flamedoge 9y ago
    I went from GMail -> Inbox -> GMail -> Thunderbird

throwaway181986 9y ago

Agree: I have similar performance issues with Google Inbox. E.g. I'm unable to attach files sometimes, and the interface is terrible. Still, I've switched to the new FF as my browser of choice and with the exception of those few sites it's great

albertgoeswoof 9y ago

Google inbox is terrible on ff, this is vendor lock-in by google, the new MS

hutzlibu 9y ago
Any proof of that claim? (that it is intentional from google and not just a ff issue?)
- kuschku 9y ago
  Google didn't even make Inbox available on Firefox for months because they didn't care, and when they did, they ended up serving entirely different HTML and JS to FF. This is the same Google that is still keeping Allo Web and Google Earth a Chrome exclusive, the same one that has paid adware vendors to sneakily install Chrome, etc. Sure, you can believe that this is jist a coincidence. But that's one unlucky streak of coincidences. In fact, you'd be more likely to win the Powerball ten times in a row than for all this to happen by coincidence.
  - what_ever 9y ago
    Allo web has been available on browsers other than Chrome for a while - http://www.androidpolice.com/2017/10/03/allo-web-adds-support-firefox-opera-ios/ http://www.androidpolice.com/2017/10/03/allo-web-adds-suppor... This gives a good reason why Google Earth is only on Chrome - https://www.reddit.com/r/linux/comments/66ao68/new_version_of_google_earth_runs_on_chrome_only/dghvg1p/ https://www.reddit.com/r/linux/comments/66ao68/new_version_o... Disclaimer: I work at Google but not any of the related teams. I was curious myself about these so I Googled and came across the above two articles so these opinions are of my own.
    - robin_reala 9y ago
      Any chance you could poke the Hangouts team to get that working in Firefox? At this point they’ve have 28 months public notice that Mozilla would be deprecating NPAPI.
      - gsnedders 9y ago
        Hangouts works in Firefox Nightly now.
        robin_reala 9y ago
        Oh! Great news, it didn’t when I last tested a couple of weeks ago so I’d assumed there was no progress.
untog 9y ago
Not really, it works fine on Safari.
- kbenson 9y ago
  Which shared a lot of roots with Chrome. It's probably that they are optimizing for things that are fast in Chrome's JavaScript engine, which isn't necessarily what's fast in Firefox's Javascript engine.
  - lod723 9y ago
    Safari's JS engine is different than Chrome's though, no?
    - kbenson 9y ago
      Yes, although I'm not sure (and can't find god info on) whether they started from a similar lineage, or even if they just happen to just share some similarities that Mozilla's doesn't. If SquirrelFish (which became Nitro) happened to start with a similar architectural base, that could predispose them to make similar choices over time (e.g. if arrays are extremely efficient because the underlying types are well implemented, that could have survived and influenced later decisions. Array performance regressions might be seen as bugs that stop progress, and would possible cut of possible avenues of advancement). There's a decade of history in these engines with a lot of man hours put into them, and they were actively competing with each other very loudly for a while. There's little you could tell me I couldn't find some possible narrative justification for if I consider the PR, bureaucracy, talent and design decisions that might stem from those over a decade.
      - gsnedders 9y ago
        V8 and JavaScriptCore were written entirely independently; there was little influence between the two. V8 started as an empty codebase, not a fork of JSC.
notatoad 9y ago
Google Inbox is also pretty terrible on chrome for me, i'm not sure i'd blame vendor lock-in.
- flamedoge 9y ago
  I went from GMail -> Inbox -> GMail -> Thunderbird