I have another suggestion which I'm sure played a large part in this. SVC was an unwanted child. It wasn't their "product". One employee was tasked to write it

I have another suggestion which I'm sure played a large part in this. SVC was an unwanted child. It wasn't their "product". One employee was tasked to write it to save paying money to a "seemingly innocuous middleware SaaS". To anyone in ORG working on it, it was a dead end. No one wanted to own it and perhaps no one did. A team was asked to add features to it. Doing the ground work of actually understanding SVC had many negative consequences: * It would take a very long time, making managers not happy. It would be largely a wasted effort, since no further work was then needed on SVG. * If you became an expert on SVG, it would be yours to keep and no one wanted that.