I would be mortified, obviously. It’s libre software so others can hack it, learn form it, create variants. Not because I sought to make it easier to take me out of the picture. When I quit, Andrew Belt made it clear that it’s all business, we’re not here to make friends around here, I remember he told me to cover my own bases. I covered them by quitting: it would be extremely hard to find a developer who is both willing to start an hostile fork, and who has the skills, taste, and dedication required to uphold my quality standards.
Mog’s a long time friend, someone similar to me in many ways, and a very private person without much of a public internet presence. I just wish to set the record straight on this: they didn’t quit in reaction to what I said. They had actually quit before me, for the same reasons. Like most people who quit, they did so silently at first.
I think you’re accidentally making the point I was trying to make far better than I did: you see a developer state that the current version has severe UI issues, yet you will tell her you have the skills and the credentials to second-guess what she said about her own software!
A simple visual comparison with v1 will surface many issues (you don’t even need to run it, you can cross-reference with the docs). The specular highlight layer on the jacks is entirely missing. The status LEDs are offset from their sockets noticeably, and when dimmed, their light blending mode makes them too desaturated. Backlit knobs lack their two-tone bezel, and their tick should be pink with a blue outline instead of black (which is a legacy codepath for Lights Off support, that no longer serves any purpose). The exact colors, along with the rest of conventions the design system and provisions made for colorblind accessibility, are documented in doc/design.md.
You tell me “Job’s done”? I tell you I would be ashamed of releasing UI in this state. No job has been done, a minimal compatibility hack has been applied. That’s not meant as a slight against Falk, it’s just a factual description of what is offered.
That’s what VCV loses by treating developers as disposable: their software, in turn, becomes treated as disposable.
I certainly would love to, too. I can’t help but feel great regret looking back at what I released: I quit before I got to get started. Starting this without experience in C++, audio development, or owning any modular hardware, made me face an uphill battle. But by the time of my last release, I no longer felt limited by my C++ skills. Were VCV a different environment, I would have achieved so much in it.
But we all know what the problem is, don’t we? It doesn’t matter one bit how nice we might be to each other. The Code of Conduct doesn’t apply to the one person who makes it miserable. And after my participations were erased, it was changed specifically to forbid such discussions.
In fact, the only reason I checked out the community a few days ago is that I received yet another private message informing me someone chose to discontinue their involvement with VCV, for the usual reasons. I wanted to take the pulse, so to speak. I have not used VCV at all in two years, just tried out Cardinal a few times, so I don’t follow closely what happens.
Anyway, I have not disappeared, those days you’ll catch me in every friendly hardware synth DIY place. Cool people there, even some fellow ex VCV module developers.