I think it's potentially underestimating the nature of the problem and OP's complaint to simply write off potential switching costs as "inconvenient". For exam

I think it's potentially underestimating the nature of the problem and OP's complaint to simply write off potential switching costs as "inconvenient". For example if I've developed a whole workflow around keyboard shortcuts, APIs, whatever, for manipulating a set of data using an app, and then that app disappears, even if I have the underlying dataset it might take me quite a while to get up to speed with a suitable replacement. All of that might argue against investing heavily in developing expertise with a closed, indie, proprietary, or even an OSS app[1]. Ultimately whenever you invest your time in developing a skillset or workflow you are inherently also obligated to evaluate the future risks involved. [1] Despite it being OSS, if it becomes unsupported and stops working on newer OSes/platforms and no one steps up to do the non-trivial work, or host the servers or whatever, you're still in the same boat.