• pup_atlas@pawb.social
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    I work in tech, and I’m still using Chrome. I don’t like it, and I know a lot of other tech people are in the same boat, but I can’t just switch. That’s what I’m working towards, but the amount of tooling we use every day that depends on specifically Chrome is, significant to say the least. This is tooling we built internally to help ourselves, that depends on Chrome-specific APIs that are either different, or do mot yet exist in Firefox.

    We’re working to port this stuff over to Firefox, but that takes time, and not everyone can just drop what they are doing to reimplement the tooling they already have in a different browser. On top of userspace tooling, we also have tens of thousands of unit tests based in some part on chrome (through tools like jest and puppet) to validate certain aspects of massive distributed web platforms that cannot easily be unit tested in normal code (though we have high coverage where we can). These also need to be ported, and are VERY specific to Chrome (or Chromium in some cases) in particular. We’re talking entire teams of people, and tens of thousands of man hours.

    A lot of users truly can just switch at the drop of a hat. The UI switch is annoying sure, but its doable. For a lot of users in the tech space though, it’s just not feasible to drop Chrome overnight. We’ve started the process to be clear, but it’s going to be a very long transition.

    • WuTang @lemmy.ninja
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      So, you are not using Chrome for the web? if it is not for the web, it’s fine you don’t have to switch :)