this post was submitted on 27 Nov 2023
1726 points (97.6% liked)

Technology

59287 readers
6276 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
1726
Why Bother With uBlock Being Blocked In Chrome? Now Is The Best Time To Switch To Firefox (tuta.com)
submitted 11 months ago by [email protected] to c/[email protected]
328 comments fedilink hide all child comments
 

Why Bother With uBlock Being Blocked In Chrome? Now Is The Best Time To Switch To Firefox::Choose the browser that best suits your privacy needs.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 28 points 11 months ago (4 children)

It's weird how lots of devs treat chrome as a standard, even though when developing I have a lot more issues with Chrome browsers than Firefox browsers

[–] [email protected] 7 points 11 months ago

Well the market share is the whole story when it comes figuring out whats the standard

[–] [email protected] 7 points 11 months ago (2 children)

I haven't had any issues with browser compatibility since IE. Occasionally Safari might have some CSS issue, but it's been probably 10 years since I had any major issues with browser compatibility. Html 5 and CSS 3 tend to work across all browsers without issue.

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago) (2 children)

Across all two of them.

I would really like to see how broken the web would be if someone in theory create a new complete implementation of the basic standards.

[–] [email protected] 1 points 11 months ago

Three: Chrome and friends, Safari, Firefox

[–] [email protected] 1 points 11 months ago

There are some niche features Mozilla refuses to accept like WebSerial and WebMIDI, but they're starting to come around on them.

[–] [email protected] 5 points 11 months ago

I think devs go chrome first and then adapt the site to firefox.

[–] [email protected] 4 points 11 months ago (1 children)

Because Chrome rendering and dev tools are effetely superior to Firefox. That's why.

[–] [email protected] 1 points 11 months ago

I'd disagree on Dev tools. Both are really great and useful. What I'd say is that Firefox may have less support for external debugging, but that's more others choosing not to do Firefox debugging