It's really great for post-fight analysis and not just for e-peening on the damage meters. Often the most useful thing in Recount is the Death log, so you can figure out how the tank went from 80% to dead in 3 seconds and think of a way to counteract it. It's a little saddening that the author is neglecting it without a word to its users.
Recount was great, but I have swithced to SWStats for the /SWL (the log feature). Recount was a great tool and I will come back if it is revived and improved upon. I was also looking forward to Relog (the logging feature), but he disappeared before that could happen. Hopefully nothing catastrophic happened to him.
One of the things I liked about Recount was that it did synching. It meant that you could be pretty sure that the data was accurate if you had a few Recount users in the raid.
The most pressing problem as far as I can tell is that the in-combat realtime synching is sending so much data through the addon comm channel that it's lagging people and causing errors. I personally have never experienced this myself, but I think there are only two Recount users including me in my normal raids. So it may be that a larger number of Recount users in the raids causes the problem to arise.
There's one guaranteed solution: synch after combat ends like DamageMeters does. That has the drawback that you won't have data for "Current Fight".
There are also other possible solutions that keep in-combat synching: compressing the data (although it's probably fairly compact already); sending data in batches every X seconds with each instance of Recount in the raid negotiating with the others for a particular time-slice (although this may fall behind). I am uncertain how effective these solutions would be since I'm not familiar with the synching code.