Mon Apr 29, 2024 12:25 pm
I imagine one of the sticking points is that they currently share the same configuration files and library (database) so if a new version updates those files, the older version may not be able to access them any longer. On Windows there may also be DLLs (shared code libraries) that are shared between installations that get overwritten by a new install and become incompatible with the old installation (I have no idea if Resolve suffers from this particular issue, though because I've heard of people doing a side-by-side installation in Windows - it's just not recommended).
Having said this, since it seems you can install a beta version and then roll-back to an earlier version (except for updated projects and/or databases that were migrated), the issue with invalid configuration files does not seem to be a real issue (or is silently handled - I don't know).
Time Traveller
Resolve Studio 19.0b1 | Fusion Studio 19.0b1 | Win 11 Pro (22H2) | i9-7940x, P4000 (536.96, 8GB VRAM), 64GB RAM, M.2 boot, SSD scratch, RAID10 data | (laptop) 16" MacBook Pro M1 MAX, 32 GPU cores, 64 GB RAM, 2 TB SSD, Sonoma 14.4.1