6 ms·

Didn't Mozilla fire their devtools team ? FF devtools weren't up to Chrome as-is, and doesn't sound like they ever will be. FF seems like a sinking ship, not wo

Didn't Mozilla fire their devtools team ? FF devtools weren't up to Chrome as-is, and doesn't sound like they ever will be. FF seems like a sinking ship, not worth investing time in. TBH I'm perfectly happy with Chrome and using Google accounts. The benefits of my data following me around seamlessly far outweighs the downsides of Google having access to it.

Ygg2 5y ago
I hope you like ads, cause Chrome will be choking on them. Used Chrome on mobile once. Remembered why I don't.
12ian34 5y ago
To your second point, what does Chrome's browser sync do that Firefox Sync doesn't?
dkdk8283 5y ago
Firefox also fired their security team.
- Ygg2 5y ago
  Really? Have any news regarding this?
  - dblohm7 5y ago
    It's not true. See my reply to their comment.
    - deleted 5y ago
      [deleted]
    - exmozilla 5y ago
      I was there too. You and GP are partially correct. IMO foxsec's capabilities were still gutted in the end but the entire team was not laid off.
- dblohm7 5y ago
  This is false. (I am a former Mozilla employee who was there when the layoffs happened) This is what I know about what happened there: There were two enterprise IT teams with similar duties but different purviews. When management was deciding on layoffs, they decided to unify those two teams. Unfortunately that meant that there were redundancies. My heart goes out to those who lost their jobs, and they have every right to be upset. But the inferences being made as a result of the resulting tweets just weren't true: this notion that all security teams were wiped out is false. And there are now others assigned to threat management. Furthermore, the security teams that work on Gecko and Firefox were left mostly if not entirely intact. The entire hardening/sandboxing team was still intact: https://twitter.com/gcpascutto/status/1293519587967983616 https://twitter.com/gcpascutto/status/1293519587967983616 TL;DR: Don’t base your understanding of an organization’s capabilities off of one tweet.

Ygg2 5y ago

I hope you like ads, cause Chrome will be choking on them. Used Chrome on mobile once. Remembered why I don't.

12ian34 5y ago

To your second point, what does Chrome's browser sync do that Firefox Sync doesn't?

dkdk8283 5y ago

Firefox also fired their security team.

Ygg2 5y ago
Really? Have any news regarding this?
- dblohm7 5y ago
  It's not true. See my reply to their comment.
  - deleted 5y ago
    [deleted]
  - exmozilla 5y ago
    I was there too. You and GP are partially correct. IMO foxsec's capabilities were still gutted in the end but the entire team was not laid off.
dblohm7 5y ago
This is false. (I am a former Mozilla employee who was there when the layoffs happened) This is what I know about what happened there: There were two enterprise IT teams with similar duties but different purviews. When management was deciding on layoffs, they decided to unify those two teams. Unfortunately that meant that there were redundancies. My heart goes out to those who lost their jobs, and they have every right to be upset. But the inferences being made as a result of the resulting tweets just weren't true: this notion that all security teams were wiped out is false. And there are now others assigned to threat management. Furthermore, the security teams that work on Gecko and Firefox were left mostly if not entirely intact. The entire hardening/sandboxing team was still intact: https://twitter.com/gcpascutto/status/1293519587967983616 https://twitter.com/gcpascutto/status/1293519587967983616 TL;DR: Don’t base your understanding of an organization’s capabilities off of one tweet.