Understanding that trying to maintain so many versions of code not only takes significant time and resources that could be put to other use, if you just want to be sure to file it right, why not just get rid of the stats page completely? Not being here to argue, isn’t this feedback all just meaningless – if you are trying to provide the best experience for as many people as possible, if new features can break things in old code, if the stats page does limit new feature development?
So I call the question: As stats are supposed to be connected to performance, and as my ego is connected to stats, if you write for an audience in the first place – We'll always work on optimization – were your stats ever believable in the first place? Why did you, at WordPress, in the beginning, offer a stat page?
Matt, as someone there at the beginning, in the “you get what your pay for” in the Age of Information world, concerning a lot of tables and graphs, are your sorry that your very very good old stat page, now changed, was offered in the first place? If these numbers on the stats page had been believable in the first place?
If WP data has lost value – “If I can get exactly what you're after I'll FILE the request.” – this sure sounds like real work at the Service Desk over these complaints by the minority who were using the old world data, with the tension between the celebrated diversity of the world – with secular policies advocating minority rights – and new-timers who insist that the central organizing principle of technology is coding and new features-to-come. But isn’t blogging going in the many-versions-of-code-world the way of the daily press where WORDS are getting replaced by numbers, in order to stay updated with technology, and nobody is reading but, like me, just complaining?