Yeah I know, I was just pointing out something. When you come across so many ROMs that are so similar, how do you know you aren't going to end up in another situation like that? Because really, ALL of these ROMs are so similar, its hard to find anything different between them. They even suffer from the same bugs. So, actually devs aren't creating anything new; they're just retheming the same ROM. /
Sent from my Droid Razr M using Tapatalk 4
We know exactly where all the code in a ROM came from. If the commit history matches then we know that they slapped their name on it with some other guys code under the hood.
All these ROMs? I'm on CodefireXperiment for mako right now, and it is a ROM just how you would describe, similar to others. There are HUGE differences in the way the ROM is built however. Toolchain compiled at build time for mako, with -O3, with Link Time Optimization with a few other build system enhancements. My point is from the user point of view all these ROMs could be "similar" in aesthetics and features. But from a build system and code point of view many are very different.
Another example is uXylon. They merged together all the frameworks(features) you would want. But they did something unique. They created an app called uTool to pull all of these features together into a tight, organized menu instead of spread all over Settings.
Whether the difference be in aesthetics, in code, or how the ROM is compiled, why does it matter? The more others can reiterate what has already been done the more it is refined and the more users benefit. That's open source.
Sent from my AOSP on Mako using Tapatalk 4