I have jBridge. Any other reasons to go with 32bit? The reason I ask is because I don't really know the difference. Is one better than the other? If my systems runs 64, and it does, should I just go with 64? I "think" I'm also concerned with compatibility issues. As in, if I create tracks in 32 bit BIAB or RB are those fully functional in Reaper?
If you buy Reaper you can download and use both the 32bit and the 64bit (and what you save in both Reapers can be loaded by both Reapers. In that sense there is no difference between the 32bit and 64bit)
Audio-tracks exported from BIAB or RB can be loaded in either Reaper version.
I personally almost exclusively use Reaper 32bit on a 64bit PC (because some of the VST effects I use are 32bit only and my projects are still not too memory-intensive to fit into 32bit)
There's a learning-curve, as with all software, but Reaper is well-documented so it's actually fairly easy to find out what you need to get something done (and via google and youtube it's hard to get really stuck, so in that regard it's not difficult to use)
Reaper can be very powerful, but you won't need to master any of this power before you need it. In that way Reaper is very clever. You can automate almost anything, but you don't need to worry about learning this before you want to do it. So Reaper allows you to work and learn at your own pace, which is really the most productive way to work (in my opinion)
Very pleased Reaper-user here

Oh, and stability is rock-solid (unless you try to load VSTs or plugins that are unstable, or perhaps some audio-infrastructure that isn't solid. I use Reaper with a Roland USB-soundcard that provides its own sounddriver infrastructure, so I can't say if all ASIO drivers will work equally good. Also, latency settings can make a difference and so on, I believe it's like that with all DAWs) with no bloat

(the download is so small it's almost unbelievable there's a real piece of quality-software in it

Other programmers could learn something there!)
JEL