3 ms·
The biggest problem with OpenSolaris was proprietary blobs required to build it. Do you know if Fuchsia has any of those? If it doesn't, then just fork it.
by gtirloni 8y ago
The biggest problem with OpenSolaris was proprietary blobs required to build it. Do you know if Fuchsia has any of those?
If it doesn't, then just fork it.
- bayindirh 8y agoWhat I'm trying to say it, it'll probably end like AOSP. Downloadable, buildable, but useless without vendor or closed source add-ons/drivers. Forking is always easy, maintaining is hard. Also, we're not sure whether things will be made harder by Google when things get mature.
- gwilkes 8y agoI think useless is going a bit far, isn't Fire OS a fully maintained fork? I believe there are some maintained forks in China as well but I know less about those
- bayindirh 8y agoYeah, useless a bit too far to generalize, you're right. But, in the end, it will won't be usable by general public or software hackers (in its original definition). I don't have any Android devices, and I don't follow its forks, derivatives or general state too closely. If you have the money and the means, you can always make a fork of an open source software and make it work for you. To be more accurate, maybe I can say it won't be very useful for the general public, but big companies can do whatever they want since they have the money and the man-hours.
- juliangoldsmith 8y agoFire OS is a fully maintained fork, but it still requires proprietary blobs to be functional. As far as I know, there are no commercially-supported Android forks that have open-source drivers outside of the kernel.
- usrusr 8y agoA clean cut between a free core and the adtech layer should be a welcome property. Think Chrome/Chromium, not Android/AOSP. For AOSP, our perception is dominated by all the trouble that derives from hardware vendors forcing binaries into a kernel that actively rejects them.