• 0x0
    link
    fedilink
    arrow-up
    2
    ·
    7 hours ago

    glibc is key here, it’s what most linux distros use. One of Google’s vendor-lock moves was to start using their own libc implementation, making it incompatible with everything else.

    • boredsquirrel@slrpnk.net
      link
      fedilink
      arrow-up
      1
      ·
      7 hours ago

      I can imagine that theirs is safer and more suited for targeted devices. Linux is extremely generalistic and has a ton of cruft.

      But I have never looked at their code or tried to port a Linux app to Android. The #Krita devs might have some insight here.

      • 0x0
        link
        fedilink
        arrow-up
        2
        ·
        7 hours ago

        I can imagine that theirs is safer and more suited for targeted devices. Linux is extremely generalistic and has a ton of cruft.

        For targeted devices so is Gentoo. Their edge is having access to proprietary drivers.

        But I have never looked at their code or tried to port a Linux app to Android. The #Krita devs might have some insight here.

        If it’s written in portable C you can use the Android NDK/SDK to cross-compile it for the 4 archs they support. I do it at work.

          • 0x0
            link
            fedilink
            arrow-up
            2
            ·
            4 hours ago

            Not an actual lock-in as they (still) provide tools to cross-compile and the source is (still) available, more like a vendor push-out if you insist.