• 0 Posts
  • 69 Comments
Joined 6 years ago
cake
Cake day: January 17th, 2020

help-circle

  • Because of lack of standardised firmware on smartphone. PCs uses UEFI + ACPI to give information about devices to OS, on smartphone world different chip manufacturer have different bootloader and they load linux kernel and pass DT(device tree) which explains what devices are present and also smartphone were used to be less powerful, contains less storage (in past) so what they do is to compile linux with only the drivers which are actually present on that particular devices to save space. Thats why a smartphone rom is not a generics image which will run on all phone. But android/linux can be compiled like a generics image, look androidx86 project for example.
















  • the_lone_wolf@lemmy.mltoPrivacy@lemmy.mlPlease, do not use Brave.
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    2 years ago

    maintaining a custom fork of a very active software project is very hard bcz google maintains chromium and they don’t have to ask anyone if they want to add or remove something from their project but if you are a maintainer of a fork who adds more features and don’t upstream your changes(in brave case google will not accept pull request from them for the feature they already remove like Manifest V3) maintaining the patches and constantly porting them to the newer version is a pain in the ass and imagine yourself working against large team of google engineers, they get paid to do this but not lots of people have resources to keep fixing all the PRs from Google devs which they make to break the adblockers to maximize Google profits.

    its far better to use a browser which was made from ground up to support user privacy and features rather then patching a browser which was made to compromises their user privacy