Hi, I have to chip in as a sole developer as well, and agree with Corky.
You fit development around other things. Some additions to your code base are trivial and you can keep doing drops with little testing or impact on your code base. Other changes are massive such as an OS X Port or VST3, and they will take time, and you need to prioritise adding features like that, which maybe 10% of your users are gagging for, compared to the 90% you have needs that are simpler to implement.
Case in point my kronos.factory librarian. I had planned to release well over a year ago. But the complexity of the file format and that fact that my beta testers persuaded me that I need to support older file versions, coupled with the demands of my day job, and setting up a new set for Welsh Floyd as well, means that I am still not quite finished on kronos.factory…
Five years ago, probably everything had a VST2 option, it is probably only know that some manufacturers are deprecating VST2 and I guess Steinberg would be the first.
I will be pleased when Brad does add VST3 support as I can do a lot of rationalising of plugins, but it is not a show stopper for me, and I’d prefer Brad to “do the job right once” if it’s feasible.