It is hard to argue for or against Ripple because the information about the system is so scarce.
Ripple official website, and the Wiki were badly written, perhaps by some pre-school kids, and have failed miserably to articulate the value of the system. I have to wonder how all the proponents in this forum derives the additional insights. Perhaps, they can volunteer their service and help Ripple to update their website/wiki.
Looking at all the 4 possible P2P payment scenarios:
Scenario 1 - End-to-End crypto currency payment.
A (send cryptomoney) --> crypto network --> B (receive cryptomoney)
Scenario 2 - Crypto to Fiat:
A (send cryptomoney) --> crypto network --> Crypto2Fiat Gateway (such as BitPay) --> Gateway's Bank --> B's Bank --> B (receive money)
or
A (send cryptomoney) ---> crypto network --> B (receive cryptomoney) --> crypto network --> Crypto2Fiat Gateway (such as BitPay) --> Gateway's Bank --> B's Bank --> B (receive money)
Scenario 3 - Fiat to Fiat
A (send money) --> A's Bank --> Gateway (such as Paypal or Dwolla) --> Gateway's Bank --> B's Bank --> B (receive money)
or
A (send money) --> A's Bank --> Direct Wire Transfer --> B's Bank --> B (receive money)
Scenario 4 - Fiat to Crypto
A (send money) --> A's Bank --> Gateway (MTGOX) --> B (receive cryptomoney)
Kindly explain, how would adding Ripple into the transaction flow any of this scenarios help to make P2P payment transactions "faster, easier, or cheaper" [as was described as part of Ripple's benefits]
If you have any currency, crypto or fiat, with reasonable liquidity either in the Ripple system or in any system the federates with Ripple, you can make a payment in any destination currency (that has reasonable liquidity) to any other Ripple user or user of any system that federates with Ripple, in a single step with a single Ripple transaction. So if you have US dollars on PayPal, and PayPal federates with Ripple, and you want to pay Bitcoins to a user of Dwolla, and Dwolla federates with Ripple, you can do that with a single transaction and it "just works".
The point is that you don't have scenarios any more. It's just like email. In the early 90's, we had "AOL user emails CompuServe user" as a scenario. I can see you arguing against Internet email saying "Now, Compuserve just sends the email directly to the final recipient. With SMTP, CompuServe has to hand the email to an SMTP server, and AOL has to run an SMTP server, and each end needs a gateway, and it's *so* complicated". But of course, email that isn't federated is unthinkable today, and all these "extra steps" are totally invisible to users. They just enter an email address and the email gets there. Federation through Internet email made the idea of different scenarios completely irrelevant. That's what Ripple can do for payments.
All these different scenarios show exactly the problem Ripple is trying to solve. In each scenario, take the point closest to the source that supports Ripple and the point closest to the destination that supports Ripple and replace everything between them with a single Ripple transaction that has a transaction fee of a fraction of a cent and can draw off liquidity (and competitive rates) provided by anyone else who uses Ripple and that completes in seconds.