Many things new and different are perceived as difficult or pointless.
I think one of the problems is the change towards the “known” way of coding plugins. E.g. in that thread above it is stated that there is a “simplified” option when programming a VST3 plugin. Why is there a simplified version at all? Because it makes it possible to take your current code base and slap in there. Voila, I now have a VST3 plugin, with no VST3 features, other than the ones possible by simply compiling it using the VST3 plugin framework.
However, it appears a VST3 plugin needs a few things that are very different from the traditional plugins architecture, e.g. a separation of church and state… pardon me, I meant of course the UI and the worker thread, modifying the audio engine to accommodate individual note expression, etc. This means a different approach to “programming plugins”. This in turn means that the traditional plugin formats needs accommodation, etc.
A developer typically wants provide the cool stuff, and so jumps into full VST3 adaption mode and can easily end up with a “fail”, simply because of the magnitude of change needed. Imagine having created this awesome synthesizer engine, and to find out that you have redo it differently. Unless you’re born to code these things, this will be a hard struggle, and some will end up saying “this sucks”, skip the whole thing and argue all the way.
Am I making a claim that the standard is without flaw? Certainly not, but keep on b*itching is not a solution. Trying to fix the actual faults is. Communicating actual faults and arrive at some decent compromise is. I mean, HALion 5 works, which means it can be done. The question is what does it take to get there?
IMHO, it is worth it, as a consumer. The functionality provided in VST3.5 is just simply fabulous, HALion 5 is the show case to which all other plugins should be measured. I am not referring to the audio engine itself (so don’t get your knickers in a twist) but to the features provided by virtue of being a (not “simplified”) VST3.5 plugin.
BTW, do you know who wrote version 3 of the VST plug-in specification? It was Matthias Juwan from the Studio One team.