Quote Originally Posted by GreatEmerald View Post
Well, with the dual license, I guess that one thing people wouldn't like to see is it turning into what OpenAL is now - a once open-source project turned proprietary, with the proprietary part having all the really good features (EFX equivalent to EAX Advanced HD 5.0, for instance). OpenAL Soft couldn't match what Creative did, so what makes you certain that it will be different with Qt, in case the company that owns it turns the project proprietary?
The KDE QT agreement kicks in and Qt goes BSD licensed?