But I fully understand that for a graphical modder or a player it may seem boring ... (simply because you do not face the issues we programmers do).
This is why I don't really see the point in the poll this time. The target audience for this thread is mainly programmers.
- stability improvement (bugfixing and avoding bugs)
- effort reduction (for future features)
This is the essence for non-programmers. Think of programming like driving from home to work. You can pick multiple ways to get there. Some are faster than others, some requires more effort (traffic etc), some are more prone to crashes than others. It's kind of the same with programming. It's possible to write code, which is more prone to future bugs than some other code even if the two pieces of code seems to be doing precisely the same. The same goes for how friendly it is to add new features in the future, how fast the game is running etc.
This proposal is mainly about ending up with the same gameplay (more or less anyway) while removing parts of the code, which makes future additions more difficult and are prone to cause future bugs. The fact that it can be used to reduce the time we have to wait for the next turn is also attractive.
Writing this reminds me of one of my first "from scratch" feature I wrote for any Colonization mod. It caches the yield cost for professions instead of calculating from scratch each time. The gameplay is 100% the same, but it reduced the waiting time for the AI by 17.5% (40 to 33 seconds in my test savegame). Without caring for the internal change, players would still benefit from the reduced waiting time. Needless to say this cache is included in WTP.