@RobElliott @Helmuti_pdorf, thank you for understanding. As it was already pointed out, we need to prioritize our work. We try to fix bugs and make it a priority over implementing new features. Nevertheless, sometimes we need to work on code improvements. Code refactoring, though invisible for users is really important for the whole service performance. As you all know, the ListPages module is one of the most resources-eating functionality of Wikidot.
I could say that we can choose between new features or performance. In fact, we cannot choose, because the performance of whole Wikidot is and will always be a no1 priority.
@James Don't think that I'm rude, it's not my purpose. We do not have to report every change we do in Wikidot, we do not have to consult everything we do. You do not have the right to request such behaviour from our side.
We try our best to improve Wikidot in the cooperation with our Users, we listen to you, implement features you want the most, consult ideas and design things using your help and suggestions. But you have to understand, that it's not working in a way: "I will design it and you guys will implement this in a way I want". Wikidot has it's own internal roadmap, some things may be done, some not - from various reasons - starting from code complexity, possibility of making changes, performance issues, ending on changes' worthwhileness for Wikidot as a whole service.
We know that you guys don't like it, but either we give green light for ideas or just say 'no', whatever we do, we have our reasons and for the good of the Wikidot as a project and for Wikidot Inc. as a company we just do not explain our decisions.