6 ms·
"parts of the UI stayed closed source" If anything is closed, except drivers they'd likely be forced to accept binaries for, I wouldn't even consider the OS. W
by jasonkostempski 9y ago
"parts of the UI stayed closed source"
If anything is closed, except drivers they'd likely be forced to accept binaries for, I wouldn't even consider the OS. Who do they think their target audience is? I imagine most people looking into an alternative mobile OS are well aware of the slippery cliff that is proprietary software. It's the whole point of looking around. I'm looking for full control so I don't get stuck with someone elses bad choices yet again.
- robertAngst 9y agoDo you develop for iOS?
- Mediterraneo10 9y ago> Who do they think their target audience is? Large corporate clients like the Russian postal service. While Jolla has always drawn on bug reports and some contributed code by hackers who are passionate about owning a cool, supposedly open-source phone, the company has never seen that audience as big enough to generate profit. Jolla has been striving for years to win adoption from sectors that don’t really care if the code is completely open or not.
- rqs 9y agoHow about another angle: Android is Open Sourced and much powerful than SailfishOS. It's much easier for their target audiences to targeting Android than their OS.
- realusername 9y ago> Android is Open Sourced Only partially, the ASOP does not run on anything because of the vast amount of blobs and basic drivers missing and people are maintaining open-source reimplementation of the gapps to make even the most basic apps working.
- simonh 9y agoTrue of course, but: 1) Any other open source OS would have exactly the same problems. And 2) They wouldn’t be any easier for them to solve, so why not concentrate efforts an solving it on AOSP which already has an ecosystem? Yours is an argument why all struggling OSS mobile OSes are struggling, not particularly why AOSP has problems. Surely if even AOSP is struggling to solve these issues, what chance do the others have?
- realusername 9y ago> Any other open source OS would have exactly the same problems Not to the same degree, Linux still has some blobs to run on modern computers but nowhere near as much as Android. Android needs blobs for absolutely anything. And you don't need an equivalent of the Gapps on Linux, it would be like something as common as systemd would be proprietary. > Yours is an argument why all struggling OSS mobile OSes are struggling, not particularly why AOSP has problems. Surely if even AOSP is struggling to solve these issues, what chance do the others have? Google does not care any more about open-source on Android, the current open-source bits are just there because of legacy history, they close all the open-source parts step by step. The Gapps used to be open-source at the beginning. AOSP isn't struggling, it's just there's no open-source movement.
- sangnoir 9y ago> Not to the same degree, Linux still has some blobs to run on modern computers but nowhere near as much as Android. Uhh, come again? Android driver blobs are for the Linux kernel that Android uses, and OEMs don't bother mainlining their drivers so Linux is no better than Android, by definition. > The Gapps used to be open-source at the beginning This is flat-out wrong. GApps were never part of AOSP- or open-source.AOSP included alternative open source apps that offered similar functionality (like a mail client) > AOSP isn't struggling, it's just there's no open-source movement. Lots of projects are based off AOSP- it's not obvious because they have names like CyanogenMod, LineageOS or Copperhead. There is in fact, a vibrant open-source movement.
- fsloth 9y agoI imagine the market sector that cares and actually understands the issues is not too small in itself but in the scope of potential users of smartphones quite tiny.