3 ms·
'Obvious deficiencies'? What do you mean? There forks of both Chromium OS and Android which are successfully running for a while now.
by ktta 9y ago
'Obvious deficiencies'? What do you mean?
There forks of both Chromium OS and Android which are successfully running for a while now.
- candiodari 9y agoChromium - the codec restrictions mean you can't get WebRTC working correctly. Android - nothing works in AOSP. And I mean nothing. You'd think a Phone OS, for instance, would be able to dial a phone number.
- ktta 9y agoAre you talking about Chromium or Chromium OS? They are very different things. Both of them have working OSS forks, or just work out of the box. Chromium (Browser) - Just chromium. Works without changes (except for Widewine EME). WebRTC is an open standard, and Google primarily uses open codecs like VP9 and Opus. Can you point to something you think says about restrictions? Chromium OS - Neverware sells a fork ('support' technically) to schools. You can download it for free. Android - Dial a phone number? Are you talking about the modem firmware? That's the phone manufacturer's fault, not AOSP's. There are obviously differences between closed source versions and what you get by immediately compiling. This is true when you have a real permissive license (non-copyleft) like Apache or BSD. You can't expect a company to release little thing, especially when that involves divulging info about other products they don't want to.
- candiodari 9y agoWebrtc required codecs aren't supported for chromium/chromeos (won't work at all with apple stuff). Neither is Netflix and ... That's not a small issue. It also is not at all the only issue. I don't care whose fault deficiencies in Aosp are. I was talking about restrictions. Any app using the "default" Apis mooie mooie and more moved into the play support libs (and that's a lot) won't work. These are not trivial things at all.