It doesnt matter how high it is.
The higher the difficulty, the higher the price.
The lower the difficulty, the lower the price.
Fjordbit:
"
If the rate of difficulty change goes above this amount (36.2%) and all other things stay equal, then it will stop making sense to purchase systems and instead it makes more sense to buy bitcoins. This will drive up the price of bitcoins, lowering the btc per MH/s cost for a mining rig. It is possible the difficulty could fall if people come offline, but this is doubtful as it will still make sense to run an existing system.
If the rate of difficulty change goes below this point and all other things stay equal, then it will stop making sense to buy bitcoins and instead it makes more sense to buy a system. With more people coming online, this will push up the difficulty level.
If the exchange rate of usd to btc goes up and all other things stay equal, then the btc cost of MH/s goes down, and it makes more sense to mine than buy. With more people coming online, this will push up the difficulty level.
If the exchange rate of usd to btc goes down and all other things stay equal, then the btc cost of MH/s goes down, and it makes more sense to buy than mine. This will slow the difficulty rate.
If the dollar cost of a mining rig goes down, it makes more sense to mine than buy. This could have the effect of lowering the btc exchange rate or increasing difficulty or both.
"
http://forum.bitcoin.org/index.php?topic=20219.0
Hmm, i can't totally agree with that.
Price drives up difficulty, difficulty does not drive up price.
We have seen this when the prices were 30$+, bitcoin had a lot of media attention since then and we saw a huge increase in total network speed, thus driving up difficulty fast. If the prices stay low for a while, the total network speed will slowly increase, and the difficulty will increase slowly.
Edit: Something else:
Arent we supposed to see a huge increase in network speed and like over 90,000 topics about it since the difficulty change? Did bitcoincharts change something to fix this "bug"?