Just as an exercise for the wish list - fillers. ( including me, as I still would value threading or something similar, but can wait)
Look at the settings now. All of them.
Take every one that can be on or off, count those as having two states.
Take every one that can take variable values as having at least three, one each on the limit, one at a nominal value.
Take every major state the ui can be in,
Take every state of the phone that can have an effect. Standby/sleeping/awake, etc...
Consider how many processes go on in the background (sync,push,etc)
Now consider every version of android he supports.
Now consider every one of these in every combination of states you have enumerated.
Got a really big number? You bet!
You haven't really started to visualise the complexity, as weirdness may come from malformed data received from a server, or "user error" unforseen by the developer. How to handle that?etc, etc.....
Such combinational complexity can never be validated by exhaustive testing,in fact, but by good software design that isolates the issues, and so allows the testing to be rationalised.
Mission creep is the enemy of robust design. It is probably the main reason why big IT projects promoted by the uk government always fail, and fail truly spectacularly. When you move the goalposts, the football game suffers quite badly!
I would like kostya to continue to deliver good software, not get to the point of "code rot" or untestability that afflicts a lot of bloatware found on PCs these days.....
Just my two cents worth.
