bpt11@sh.itjust.works to Linux@lemmy.mlEnglish · 1 month agoDo any of you daily drive a mobile Linux distro on your cell phone? Is that viable / will it ever be?message-squaremessage-square47fedilinkarrow-up162arrow-down11
arrow-up161arrow-down1message-squareDo any of you daily drive a mobile Linux distro on your cell phone? Is that viable / will it ever be?bpt11@sh.itjust.works to Linux@lemmy.mlEnglish · 1 month agomessage-square47fedilink
minus-squareboredsquirrel@slrpnk.netlinkfedilinkarrow-up1·1 month agoThey dont use GNU or glibc or systemd
minus-squaredavel [he/him]@lemmy.mllinkfedilinkEnglisharrow-up3·1 month agoLots of distros don’t use systemd, and a few non-AOSP distros don’t use GNU userland or glibc, Alpine for one.
minus-square0x0@programming.devlinkfedilinkarrow-up2·1 month agoglibc 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.
minus-squareboredsquirrel@slrpnk.netlinkfedilinkarrow-up1·1 month agoI 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.
minus-square0x0@programming.devlinkfedilinkarrow-up2·1 month 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.
minus-square0x0@programming.devlinkfedilinkarrow-up2·1 month agoNot 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.
They dont use GNU or glibc or systemd
Lots of distros don’t use systemd, and a few non-AOSP distros don’t use GNU userland or glibc, Alpine for one.
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.
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.
For targeted devices so is Gentoo. Their edge is having access to proprietary drivers.
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.
So how is this vendor lockin?
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.