there’s a whole class of users born with smartphone, those were not techie or concerned, then you have the other class who don’t know really anything about these things which only use smartphones.
even discussing with family about privacy is difficult. “but everyone use it”… gosh.
then you have some of my IT colleagues - there for the good money job - which don’t care with the motto: I have nothing to hide.
anyway, stay true to your principles no matter what.
I blame these “tech youtubers” who don’t understand anything technical and keep repeating the script which the company provides them. I saw this idiot MKBHD telling his viewers how a phone has a “beast mode”.
Wtf is a beast mode? ! Non technical guys eat shit like this and proceeds to buy because the phone has beast mode lol.
These are exactly my thoughts about tech YouTubers. They have no idea what they’re talking about and encourage mindless consumption. Glad I’m not the only one who’s thought about this.
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.
there’s a whole class of users born with smartphone, those were not techie or concerned, then you have the other class who don’t know really anything about these things which only use smartphones.
even discussing with family about privacy is difficult. “but everyone use it”… gosh. then you have some of my IT colleagues - there for the good money job - which don’t care with the motto: I have nothing to hide.
anyway, stay true to your principles no matter what.
I blame these “tech youtubers” who don’t understand anything technical and keep repeating the script which the company provides them. I saw this idiot MKBHD telling his viewers how a phone has a “beast mode”. Wtf is a beast mode? ! Non technical guys eat shit like this and proceeds to buy because the phone has beast mode lol.
These are exactly my thoughts about tech YouTubers. They have no idea what they’re talking about and encourage mindless consumption. Glad I’m not the only one who’s thought about this.
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.
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 :)