I'm not sure you've understood how blockchain.info and strongcoin work. You literally don't trust them. Your wallet is held encrypted on their server, so they never see the private keys and hence cannot steal the contents.
(The above isn't entirely true, since it wouldn't be hard for them to inject javascript that stole them when you opened your wallet -- but it's certainly a number of steps more secure than a hosted wallet like instawallet or easywallet)
He understands perfectly well.
He's just saying that blockchain.info is a really really good wallet, but it just isn't a one-size-fits-all solution.
I'm certainly not arguing that it is. But the debate is about e-wallets; limiting ourselves to those only, then wallet-in-browser gives you more flexibility than hosted-bitcoind.
The point is that non-hosted wallets rely entirely on the user backing everything up properly, not forgetting their passwords, not getting a virus infection on their device etc. If that's what a user requires it's perfectly respectable, but that comes at the price of some convenience.
I'm not sure I've understood what you're saying here (there is ambiguity) because non-hosted could refer to multiple categories. To my mind there are three key types of wallet:
- Hosted bitcoind -- the private key is entirely accessibly by the provider, and the web page is merely an interface to a few bitcoind command line/rpc commands. Instawallet, easywallet, Mt.Gox, pretty much every website that uses bitcoin-funded accounts are all in this category.
- Proxied bitcoind -- the signing and management of the wallet is done entirely in the browser (or I suppose in a customised app), the web service is simply providing an online interface to the blockchain to allow querying of balances, etc. As a convenience these services also provide the ability to store your encrypted wallet with them too, but that is entirely orthogonal to the point -- you could keep that encrypted block entirely on your own device and this principle would still work. One might reasonably refer to this as a "non-hosted" service. I believe electrum is working on making such a service easily deployable, so that you would have a choice of servers, and each would be as good as another provided you have your keys locally.
- A self-hosted bitcoind -- run your own client. This might also reasonably described as non-hosted. We're ignoring this class in this discussion, since we're talking online-wallets.
Lumping blockchain/strongcoin/electrum into the "hosted wallet" category does them a disservice.
(Oh, and if you were planning on mentioning e-mail backups remember that e-mail accounts are most of the time... hosted ) More importantly they are hosted separately from the wallet service. It's not very likely that your wallet website and your email service go down at the same time. Plus, there is nothing to stop you saving that emailed backup anywhere you like while you do have access. Personally, I have all my email forwarded from gmail as well so there is a copy on my own IMAP server, which is then cached by kmail to every computer I use. That setup might not be typical, but it isn't even possible with a hosted-wallet. (Blockchain also offers dropbox backup, so you could in principle have your backup available from blockchain, email and dropbox -- all three would then have to fail for you to lose access to your funds; unlike instawallet/easywallet)
I'm not trying to argue that one of these is better or worse than any of the others, it's horses for courses here. I'm arguing that there is more to "online wallet" than just picking among basically-identical services, and people should be aware of the danger of services that don't leave you in control of your own keys.