[Samsung Galaxy Nexus] MWisBest:
Just wanted to post a quick update on what I'm doing with development work, so here goes.

One of the things I put in the changelog post pretty much right away, under the Experiments heading, was "Check for other potential optimizations to enable, maybe Link-Time-Optimization (LTO) if it is more stable than it used to be." Currently I'm working on just that. As that was one of the first things I wanted to accomplish down the road with the ROM, I thought I might as well get going on it. I think it'll be easier for me to just do things one at a time on a first come first serve basis like this. Don't worry, I still haven't forgotten about AOKP/CMKP and any features you guys have requested! With the amount of schoolwork I've gotten beginning to pick up, I ended up kinda losing time and interest to put into this project, and my hope is that with accomplishing a big thing like this that I've been putting off longer than everything else I'll regain the interest that I had when I started working on FML.

Enabling LTO isn't going to be particularly easy and will take some time (I'd estimate if I kept with the current pace I'm working at it'll be done by Friday or Saturday?), and while working on it I won't be able to put up a new build or work on much else. Once I do get LTO done, I plan on transferring over all the work with optimizing (including LTO and all the work I've done on optimizations previously as well) to an AOKP build, and then from there I will finally be able to see what has changed in AOKP since I last used it months ago to get a better idea of how to go about merging those tweaks AOKP does that you guys and I like with the rock-solid stability of CyanogenMod.

I also noticed that OmniROM appears to have gotten its stuff up on GitHub, I'll be keeping an eye on it but as of now I'm going to let it just pan out as I feel it's a little too soon right now to use it. I would expect that they'll be doing major changes and things of that nature for a little while yet, be it adding new things and fixing things that were found now that they have more people using it and testing it.

Now, to finish off this post I'm going to try and explain what Link-Time Optimization is in an easy to understand (English-language, lol) way.

Typically, a code compiler will perform optimizations on just one section of a program, and only that section of a program, at a time. It just combs through that part of the program with a microscope, not paying attention to the things around it. These sections of a program are compiled and whatnot, and then the final step of the process is to link all of those sections together to form the final program. What Link-Time Optimization does, is rather than just looking through individual parts of a program with a microscope, it'll look at the whole program at once with maybe just a magnifying glass so it can get the "big picture". Seeing the "big picture" allows the compiler to see how those individual parts of a program all link up and work together, allowing it to optimize better, smarter, and see things it otherwise wouldn't have seen with just that microscope, which will (usually) result in a performance improvement.

Please let me know if that makes sense, and feel free to ask any questions if you want to learn more about it or something. You should see how I would've explained this a couple years ago... I'd end up just shooting right over people's heads with how technical and detailed I'd get (and worst of all, I wouldn't even realize I did that!).