Hacker News Reader

Hacker News

Comment by mrbn100ful | Hacker News Reader

Parent Full thread

mrbn100ful

They are (slowly) releasing more and more components

https://forum.sailfishos.org/t/open-sourcing-proceeding/2468...

https://github.com/sailfishos/sailfish-weather/

https://github.com/sailfishos/jolla-camera

It's still more open than AOSP

View on HN

> It's still more open than AOSP

I don't think this is true at all? AOSP is completely open source modulo driver blobs (which Sailfish has too) and Google services.

One can make a fully functional system, modulo drivers, out of only open-source components using AOSP. It's not possible to do this using Sailfish; the compositor, UI libraries (Silica), and most of the "core" apps are still closed source.

If I remember correctly a lot of AOSP core apps have been discontinued though.

Yes and most people don't realize that the current "AOSP" apps are the LineageOS apps.

A true AOPS image is missing most core Apps.

I think people got too used to bundling by Apple and Google. For most of the core apps there are good and open source alternatives available.

The main point is that AOSP as a system (modulo firmware) is open source and SailfishOS is not. Also, even though Sailfish has an Android compatibility layer (though only for official devices), compatibility is most likely always going to be worse than 'real' Android.

That said, I hope that Jolla Phone becomes a success, more competition is good. Hopefully being funded better will move them to fully open source the base system.

Because no one was using them. Everyone was replacing them and shipping other apps. AOSP is very modular and customizable letting you configure what apps get included in the OS.

The Email app had been forked into K-9 Mail, which later became Thunderbird for Android. AOSP Browser no longer made sense to develop after Chromium was ported to Android. And so on. The barebones applications in AOSP have been succeeded by better open source apps outside the AOSP repos. It doesn't make sense to maintain them when nobody putting together an Android distribution would choose to use them over those alternatives.

The compositor is open (Lipstick) : https://github.com/sailfishos/lipstick

And OSS projet based on the SFOS core exist : https://nemomobile.net/, https://github.com/nemomobile-ux

Ahh, thanks for the correction, it's the window manager that's closed (lipstick-jolla-home). Regardless, I will stand by my statement that a fully open-source build of AOSP is significantly more complete and useful than a fully open-source build of Jolla.

If we're going to start counting forks, we get to count LineageOS and GrapheneOS for Android, and then the goalposts really move.

A pure AOSP distribution is now lacking a lot of basic apps. Distributions like LineageOS or GrapheneOS fill the gap with their own, but pure AOSP is totally unusable.

Googles been quietly chipping away at AOSP for years. There was a point where AOSP was actually decent, google made sure that wasn't the case for long.

I kinda wish NemoMobile would be default UI… current SailfishUI with force gestures is (for me) highly annoying…

> It's still more open than AOSP

Uh, no? How are you getting this idea?

This is the manifest file for GrapheneOS: https://github.com/GrapheneOS/platform_manifest/blob/17/defa...

It literally contains links to all the AOSP repos or GrapheneOS forks of them. You can clone these exact repos and build the OS from source. GrapheneOS provides instructions for it: https://grapheneos.org/build

I think you mean less. Since AOSP is fully open?

Reply on news.ycombinator.com