I suggest you read the article in the link if you have any questions…quote:
“In our tests here, it matched the performance of 64-bit Cubase and Sonar by loading all eight instruments. But taking it further, this presents an alternative to trying to bridge all those Waves and UAD plug-ins into a 64-bit host so you can use the odd 64-bit instrument: instead, you could use the 32-bit plug-ins natively in a 32-bit host, and bridge the odd 64-bit instrument instead.”
And another interesting thing( about the difference between jbridge and steinybridge):
In Sonar, the BitBridge happily managed four instruments, using 3.5GB RAM, and got stuck on the fifth. Swapping VSTBridge for jBridge in Cubase left it able to match Sonar’s performance in loading up four instruments. It’s almost as if VSTBridge is artificially restricted to the 2GB of a 32-bit OS.
So yes, there are limits, but this way of working opens new posibilities to solve compatibility and performance problems…that is why I posted this.