[)roi(];8123794 said:
Lol pissing contest; btw if you remember we discussed what you did about 6 months ago... Don't take the comments personally, as they are not intended in that light -- rather an expression of the difficulty to maintain a mainstream codeset around multiple forks.
Amazon btw is a fork; all the custom Samsung mods are a fork... Hence it takes time to retrofit the "mutations" onto the mainstream codeset.
Amazon chose to screw retrofitting and I believe their success will encourage companies like Samsung to go down the same road I.e. create a Samsung fork, and be damned with the time / cost waste each time Google believes it has a winner.
If anything Google's merger with Motorola and failure to produce a solid tablet OS should encourage them to fork earlier and follow Amazon's success.
Should these forks occur; know that this will result in distinctly different products... with an aging common codeset that will stem the amount of innovation possible in developer circles I.e. limited to Apis common to all platforms, or having to write platform specific codesets.
Webkit in comparison is strictly controlled ito forking... and is more true to the open source methodology I.e. evolution is done by multiple contributors, yet there is strong control by an appointed board of the main players... Not the case with Android where much of the codeset is hands off (I.e. Google specifically refrains from jointly developing new releases with all interested contributors, hence there is always a significant time required for retrofitting by it's partners)
One way to save Android IMO from forking is to replicate the webkit model. I.e. encourage companies like Amazon to stay in the fold, and to develop a framework that minimizes the amount of retrofitting required for each new release, including building standard interface layers that substantially uncomplicate the retrofit processes -- ideally this should be transparent i.e. Samsung only needs to develop a few custom drivers and the rest is mostly change ignorant.
Wow debating with you is debating with a religious person, no wonder they say Apple users are religious. (Circle jerk much?)
When I said nothing stops you from fixing Android you claim that starting another fork is a bad idea.
When I said you dont have to fork you can simply add to the main tree you complain about someone that did fork.
Amazon's fork had nothing to do with the original "well fix it" argument but in any event.
Amazon is selling a service, not a product and they wanted to limit people to use other services hence the fork. Something that would not exactly work for other OEM's as they don't make money off a service but they make money off a product. This fork forced them to run their own app sore as well, seeing that the limitations they added caused over 90% of the Android apps to stop working with the Kindle.
As for Samsung's modifications, you are aware that all the core modifications make it back into the main stream? The Hardware acceleration that we enjoy now in Android 4.0+ was a mod to the core Samsung employed back in the 2.3 days.
If you fork you limit your users access to the Google market so you better have a decent market in place to keep your customers else they will vote with their wallets and go to a competing platform that does give them access. So yes, you can fork but that is a very dangerous game to play when it comes to Android as an OS. Something that can very well happen if Motorola+Google decide to break away from the main alliance.
The other OEM's like LG, Samsung, HTC, ASUS, Dell, and
more can simply move their support to say
Appbrain. This will kill Google as the head of the Project I am sure, but will not kill the OS.
Android is simply not just one company, its the global effort of loads of manufacturers, service providers, developers and users and that is its real strength.
![[)roi(]](/forum/data/avatars/m/8/8711.jpg?1563828683){kind=avatar}
