Crazy Idea - Putting SQL Logs into RAMdisk - Thoughts?

Hello My Fellow SQL Admins,

About 8 months ago I resolved a tempdb bottleneck by creating a TempDB drive in RAM, using RAMDisk software to accomplish this http://memory.dataram.com/products-and-services/software/ramdisk. So far, it has worked great. My TempDB latency has gone down from double-digits to 0-1.

I am now shopping for a replacement server hardware for our heavily used ERP system & OLTP back-end SQL Server. While scoping my spindles, a crazy idea came in mind. The RAM has gotten so cheap and abundant these days, why not include 4 additional 16GB sticks and put not only my TempDB, but SQL Logs into RAM drive as well? :)

The one thing that scares me is there is no redundancy to RAM. Unlike TempDB, which gets recreated every time you start SQL service, it would be a pain to mitigate the loss of SQL database logs.

Heaving said that, it is not often to see RAM fail. Also, I can implement hourly transaction log backups.

What do you think folks? Would you try this, or would you rather go with a conventional, dedicated RAID10 array for SQL logs? I am very tempted :)

Thank you!