You guys are going to play on Shuffle iT no matter what happens, you all love Dominion. Casuals aren't going to play if they don't like it. So maybe listen to their complaints and cater to them a little bit.
I may love Dominion, but I like Dominion as it was on Isotropic. I stopped playing Goko when it was clear they weren't going to make it anything like that, and came back to try once on MF's client, which wasn't all that much different. I just wasn't interested in paying to play Dominion on that kind of interface, especially not buying all the sets again. And I definitely don't like Dominion enough to play a bunch of base set again and again (which is why I'm annoyed at how many Base cards seem to be in game with most people). I care more about being able to play quickly and crisply, and against players of similar skill from whom I can potentially learn things. Most people aren't like me, I understand that. But my opinion is still valid.
What I failed to mention before that was brought back up was the promise of a pared-down interface. That's something I'd definitely like to see, but certainly it shouldn't be a priority; fixing things that are broken is the priority. Nevertheless, I was under the (perhaps greatly misguided) impression, based only on my own thoughts about how I would be doing this, that you'd first build a developer's interface version primarily for testing the game engine, and then build the graphical interface over top of that, while making the developer's interface available to players who for some reason might want to play that. It might not even have been all that great to start, but it at least would have been in the minimalistic style of Isotropic's text interface that I had come to love and enjoy. But if that's not how things actually turned out, then I guess it needs to be left on the back burner for a while.
I also was under the impression that Donald X played with Inheritance on some version of the new client, and yet it's not available when the client is released. Did something in Empires break it, was that implementation completely separate from what you came up with later, or was it actually not implemented very well originally?