[thxbb12]

I did so, too, especially when I was stupid or hasty enough to buy a new camera with unsupported RAW, which is a fashion for all manufacturers.

But it's cumbersome for me: When deleting files, it's not so easy to synchronize the other type. Also, I need even more diskspace because I tend to adjust some photos rather quickly, but I develop them only if needed.

What I usually do is put the memory card in the computer and browse all images to cull most of them. I use geeqie viewer (might be linux only - not sure) which is very fast. When I delete a photo it deletes both the JPG and the RAW. I only keep the "keepers" (for instance I try to only keep a single or a couple of shots in a given sequence). Then, I import what's left in the RAW converter. This way, I don't end up with tons of images and disk space is mitigated.

Plus, storage is very cheap these days. You can get 16TB of RAID6 for less than $1500 (e.g. NAS with 4 HDD of 8TB each).

Diskspace is cheap, that's true. But with bigger or more disks I also need bigger or more back-up disks and because I made bad experiences with only one document backup, I have to have two backups. At least.

RAID is no substiture for a backup afaik. It's more better up-time in case something goes wrong with a single disk.

I was tempted to use smaller JPGs to browse them before importing the bigger RAW, but I suspect the amount of time to sort and synchronize the selection would often be not worth the effort. Of course, it's silly to import first and delete second. But I'm more silly to sort and select before and then kill the worng RAW. 

If you use the right viewer you don't have to worry about killing the wrong raw file.

My current storage policy is the following:
- internal 10TB HDD that mirrors my desktop HDD each night.
- external 10TB HDD that mirrors my desktop HDD each night.
- 16TB NAS network connected (local) to backup my desktop
- online unlimited backup service that backups my desktop HDD

So I think I'm unlikely to loose any data ;-)