on the level of functionality at which I have dealt with version control, it seemed like basic operations I could do were the same on various systems. So, wouldn’t it make sense to have a single convenient and easy-to-learn user interface that could serve as front-end for all popular version control systems, at least for those features that are sufficiently common between them? So let’s say if system X does not have feature F common to 10 other popular systems, an attempt to invoke F on the front-end would bring up “sorry, the current backend does not support this”. And if you need to use something specific to the backend that is not covered by front-end, you could just use its native interface.
I am aware of existence of plugins in Visual Studio, Eclipse etc that seek to achieve this sort of unification within the context of the app. So if we have these plugins but we do not have a standalone “version control studio” type of application that could be used regardless of IDE, is that because it would not work well? Or because the marginal benefit from such additional interface abstraction is deemed to be low, at least for experienced users?