I just started using it on my windows machine and it's getting a fair amount less stales than my BAMT box. About 0.40% stales to 1.40% stales, it's only been about 7 hours running, so it could be luck... but I think it may also be the miner.
I've been testing cgminer. It hasn't performed significantly differently than phoenix so far for me. BAMT's phoenix is somewhat customized for our purposes, and it would be considerable work to extend cgminer to have these features as well. If there does end up being a clear benefit, yes we will support it or switch to it as the primary miner, but so far I'm unconvinced.
an update on cgminer... after some more time I do like it, and it has one killer feature which is the ability to generate local work when a pool disconnects, then submit it on reconnect. I would like to eventually replace bamt's custom phoenix with cgminer.
However, it's also buggy as hell at this time.. at least the version in git atm. I really cannot use it in production. Our phoenix has proven quite reliable (well.. when wrapped with bamt magic ). I'll keep watching and testing, and hopefully at some point cgminer will be reliable enough to use in bamt. Seems the author is actively maintaining it so this might not take long.