The fact of the matter is nobody has enough information to accurate depict the stats for buying a WD Red vs WD Green. As Seagate clearly demonstrated in 2009, a firmware version that was pushed out and expected to be minor and uneventful lead to so many failed disks that Seagate had to offer data recovery services, for free. I was one of those boned by their screwup. Wasn't pretty for anyone involved. It was so severe that hard drive recovery companies had "leaked" the fact that there was a major problem before Seagate admitted to it. (One place I'd love to be an employee of is a data recovery company. They do cool stuff and I'd love just to watch them do it once.)
So even now, when it comes to buying a Red vs Green, you're literally basing your decision on data from no more recent than a month ago. Look at how long it took to find out WD Reds had the buggy firmware where they had a high load cycle count despite the fact they aren't supposed to do that.
Anyone, quite literally, is dropping big cash for hard drives that, in the big picture, you can't even truly validate are reliable or not until the money is spent and you can't send them back. Real crappy position to be in as a consumer.
Throughout my life I've always had important data that I didn't want to lose due to errors and such. I've lost quite a bit despite trying to do things properly. I'm in my mid 30s and twice lost massive amounts of irreplaceable data. In the first case it was out of my control as the data was lost *because* I wanted a backup. In the second case it was because I was serving my country and while gone I had multiple drive failures in very short succession without the ability to even know something was wrong until I got home and my g/f told me that nothing was working. Talk about coming home after not being home for 3 months to find that the entire server is down.
Thank goodness we have ZFS. For the first time in my life, I feel that my data is truly protected from the most likely outcomes that might cause me to lose my data. I never had great faith in RAID, and I was always using par2s to check the data because I lost faith in RAID controllers years ago. On more than one occasion I had files that were fine when I ran a PAR2 before doing a RAID rebuild, but after rebuild they had corruption. Not a good place to be when those kinds of problems plague hardware RAID.