With Firefox, that risk doesn't exist because of the business motivations of the company that develops it. Google may at any time change Chromium so substantially as to either require Google integration at some fundamental level for even the most basic functionality, causing too much work for such a low-profile effort to continue, or just make Chromium closed-source. IMO it's also worth noting that ungoogled-chromium is (obviously) an unofficial fork of Chromium. The code exists, but field trials should not be active unless your version of chromium was built with fieldtrialtestinglikeofficialbuildischromebranded.Most builds should be made with fieldtrialtestinglikeofficialbuildtrue, which oddly enough disables the field trials (More info here and here). Until Google inexplicably restored it a few days later, but not before lots of accusations were thrown around. Contribute to ungoogled-software/ungoogled-chromium-archlinux development by creating an account on GitHub. ungoogled-chromium overview Remove all remaining background requests to any web services while building and running the browser Remove all code specific to. Unless youre reading every line of code yourself before compiling it, Id say youre no. This notably happened with Pushbullet quite recently: Arch Linux packaging for ungoogled-chromium. Also as a word of caution, dont use ungoogled-chromium binaries. ![]() Until Google decides that your extension is unworthy of being in their store. >Extension support for Chromium is way better too Stock Firefox doesn't actually have that much bloat, and it's not noticeably slower than Chrome on reasonably modern hardware (i.e.: most page loads are near-instant, same as in Chrome on a good connection).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |