you are viewing a single comment's thread
view the rest of the comments
[+] 10 points 2 years ago (4 children)
  • [–] 65 points 2 years ago (1 child)

    There is an issue with monoculture of rendering engines. Developers assume every browser have the same things implemented and start to build around this assumption. Also Google can dictate how the web looks like.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 30 points 2 years ago (2 children)

    Exactly, we've seen this previously with Internet explorer.

  • source
  • parent
  • hideshow 4 child comments
  • [+] -2 points 2 years ago* (1 child)
  • [–] 16 points 2 years ago (1 child)

    There are two things to consider here:

    1. Adherence to Standards
    2. Creating artificial "feature" based defacto standards

    Chrome offers adherence to standards as one of their features. But it also introduces new features that look like standards, meant to increase profits for the parent company.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago

    Chrome offers adherence to standards as one of their features. But it also introduces new features that look like standards, meant to increase profits for the parent company.

    VB.Net was exactly that. Difference being Microsoft's interest was locking companies and governments onto Microsoft's enterprise products vs Google's user tracking. Easy, quick internal web app put together in half a day? Would never work right on Netscape. It takes work to make them work to standards.

  • source
  • parent
  • [–] 48 points 2 years ago (3 children)

    Using chromium based browsers keeps power over web standards and such in google's hands, i.e enforces their ever growing monopoly. So if you want a competitive/fair environment on the web, it's best to avoid them altogether and stick to firefox or safari.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 4 points 2 years ago (1 child)

    Aren't Firefox funded by Google in order to present a false sense of competition in the browser market?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 20 points 2 years ago (1 child)

    Google pays to be the default search in Firefox, it was Bing for a while.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 16 points 2 years ago (1 child)

    Also it pays to keep mozilla alive.It helps in defending anti-competitive lawsuits.

    Sad to say there are only two engines available for the open web.(Not considering Safari as that is only available on apple)

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 2 years ago

    Funny you mention Safari, because you know, Safari is the only browser allowed on iOS. Every other browser has to use Safari to render web pages if they want to be in App Store - once again the only allowed source of packages.

    Safari on iOS is literally worse than IE and Chrome combined.

  • source
  • parent
  • [–] -5 points 2 years ago* (last edited 2 years ago) (1 child)

    Unfortunately for Android, Chromium based browsers are, at the moment, significantly more secure than Firefox based ones.

    Edit: For the people down voting me, feel free to make a principled stand to avoid Chromium browsers on Android, just understand the risks. Again, specifically for Android. Here's some reading:

    https://divestos.org/pages/browsers

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago (1 child)
  • [–] 3 points 2 years ago (2 children)

    Unless the developers of other browsers take specific steps, the ad engine will get pulled on the next update of their Chromium engine, that's the problem.

  • source
  • parent
  • hideshow 4 child comments
  • [+] 1 point 2 years ago (1 child)
  • [–] 3 points 2 years ago (1 child)

    It's in Chromium, the other browsers have just disabled/patched it out: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/components/privacy_sandbox/privacy_sandbox_prefs.h

    // Un-synced boolean pref indicating if Topics API is enabled.

    inline constexpr char kPrivacySandboxM1TopicsEnabled[] = "privacy_sandbox.m1.topics_enabled";`

    e.g. Vivaldi:

    https://vivaldi.com/blog/technology/heads-up-googles-going-off-topics-again/

  • source
  • parent
  • hideshow 2 child comments
  • [+] 1 point 2 years ago (1 child)
  • [–] 2 points 2 years ago

    They have forked it though? That's why almost all the other Chromium-based ones don't have this enabled by default or completely disable it (even if you tried to turn it on).

    If you're talking about forking the entire project and using it as a base that diverges from what Google does, I don't think that's going to happen. Not even Microsoft with their billions had the desire to maintain a totally separate engine anymore and I don't see the other Chromium-based browsers redirecting efforts from useful things like better UIs, privacy enhancements, etc into just keeping feature/performance parity.

  • source
  • parent