Comment by wpasc

Comment by wpasc 3 hours ago

3 replies

im surprised this is earning such downvotes. idk about the "opinionated" vm perspective but I think it needing its own engine oe not is at least something worth considering. firefox has been my go-to alt browser for years as my backup to chrome. it was what I would use to "test again in another browser" but as time has gone by, more and more stuff just doesn't work on firefox :(

ivanmontillam 3 hours ago

It's already problematic to have Chromium dominating/near-monopolizing, and add salt to the wound letting Gecko die this way.

Chromium is so prevalent as an engine, that most developers don't test their code on Firefox and just tell everyone to use Chrome/Chromium when they run into issues.

This has the unintentional side-effect of strong-arming the W3C into compliance with the engine and not the other way around. Why do we bother with the W3C then? if they are powerless and Chromium can do as they please?

  • calvinmorrison an hour ago

    But if firefox ran chrome, it wouldn't be a problem. Vivaldi, Opera, and others are doing just fine.

calvinmorrison an hour ago

> idk about the "opinionated" vm perspective

What I mean is, it's basically a VM. It's got a screen, inputs, storage, networking.