Technology

37705 readers

362 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

167

Mozilla is eliminating its advocacy division, which fought for a free and open web (www.theverge.com)

submitted 13 hours ago by [email protected] to c/[email protected]

26 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 10 points 9 hours ago (1 children)

As for losing the advocacy group, it sucks, but if I were in a tough position where I had to choose between advocacy and development, I would stick with my core mission - a stable browser with the features that users want.

Okay but they often don't give users what they want, like telemetry, 'privacy respecting' adverts and AI etc.

[–] [email protected] 5 points 7 hours ago

Okay but they often don't give users what they want

You should see the state of Firefox on iPad OS. I started using it earlier this year after they finally rolled out support for multiple windows—a feature Safari added in 2019 and Chrome had only a few months later.

Nice that they finally have this feature, but the browser itself is nearly unusable. It stutters constantly and freezes, locks up, or force reloads with some regularity. In a way that Chrome and Edge (and I assume Safari, though I have never really used that) never do.

Or on desktop OSes, a website I frequented around 2016–2018 used the column-span CSS property, which Firefox didn't get around to implementing until December 2019.

It's been very clear for some time that, whether it's because they stretch themselves too thin or some other reason, Mozilla has been failing to continue to deliver an excellent product for their users.