Both parties deserve blame for worsening the judicial confirmation process. One of the few times its accurate to say both sides. But do you really think McConnell would've let Dems block Gorsuch indefinitely if only Reid had let GOP block lower court judges indefinitely? Come onhttps://twitter.com/varadmehta/status/1036657529445670913 …
As a general statement, sure. But we've seen McConnell undertake unprecedented actions, including on judicial confirmations. So I'm very skeptical of the argument that he was constrained by precedent, but had no choice after his predecessor broke a precedent.
-
-
"Had no choice?" I suppose you've introduced an argument easier to discredit. So, good job?
-
I'm very skeptical of the argument that McConnell was constrained by precedent and would have accepted a Democratic minority blocking a Supreme Court justice he liked in the name of precedent, because he broke precedent on judicial noms in the recent past. Better?
-
Much better. I agree with your geberal point. It's not really a McConnell specific issue. He and Reid, now Schumer, have eroded the process in innumerable ways. They're all culpable to some degree.
-
Good, glad I could clarify. Twitter privileges brevity over nuance.
-
BTW, here's a good example of "had no choice"-type rhetoric (from someone I respect). Dems "forced Rs to finish the work Harry Reid started." It was a choice. If you like it, defend on the merits. Insisting it was forced upon them abdicates responsibility.https://twitter.com/NoahCRothman/status/1036977314360373248 …
-
Nope. There's no unilateral disarmament. Dems don't get to ram their judges through and then expect Rs to surrender. So it's correct to say no choice. Rs play the same game as Dems, and now Dems are mega butthurt about it.
-
Doesn't that mean Dems had no choice when Rs blocked every lower court nominee? To be clear, I'm disputing a single point of yours: Marking the start of this cycle at Nov 2013. As if that was an actual choice, while escalations that came after aren't.
-
It goes back to the late 80s.
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.