It's time to move on. It's been time to move on for quite some time.
S0lo wrote:Thanks for your nice comments,It's time to move on. It's been time to move on for quite some time.
Sure, but isn't that the choice of the developer himself? Why should a developer be INDIRECTLY forced to use a new technology. May be his/her plugin don't really need any of the new improvements in VST 3, why should he waste time studying VST 3 while he could be improving his plugin.
When Microsoft introduced the MFC and then .NET platform. They did not remove the Win32 API. up until today, a developer can still use the Win32 API, which usually runs faster.
When Sun introduced Swing, they did not remove AWT. Developers slowly saw the advantages and moved to Swing.
If plugin developers are still stuck with VST 2, and are not moving to VST 3. Then there is either a LACK OF NEED, or there is a PROBLEM in moving. I think Steinberg should do a better job in convincing developers to move. Show really what VST3 means to them and their investment. One critical improvement is often better than ten other usually not used features.
Any established developer would keep their own backups of their setups. If they only have one copy on one hard drive, I would say that such a developer isn't very serious, or does not have a lot of experience and might as well go VST3.
There has been many discussion with various reasons why many developers have not moved to VST3 and I would say that the most piercing reasons are that "VST 2.4 could've been tweaked to accommodate most VST3 features", that "there are not enough hosts supporting VST3" or that "there isn't enough demand for VST3". If we always follow this trail, we would never get anything new. Be happy that Steinberg has platinum balls to do these things!
As far as all those other examples of keeping the past, how do look at Microsoft's Windows RT?
(I would say that they are in the same league as Steinberg in terms of sizable cojones.)
As far as I know, Windows RT does not throw the Win32 API away. Win32 API is at the core of Windows libraries, without it no program will work, including VST3 or VST2. It's solid rock into the heart of Windows. Microsoft occasionally adds new functions to it, or declares a few old functions as obsolete while still keeping them, BUT NOT totally remove it. Thats what you do with an SDK, it's not an ordinary piece of software, too much depends on it.
Correct me if I'm wrong.
Users browsing this forum: No registered users and 2 guests