The configuration management in JetBrains' products is far worse than in VSC. On the JetBrains side we have a configuration system based on a tree of XML files, some of which contain system-specific configuration and should not be checked in to version control (sometimes in the same file as shared configuration!). On the VSC side we have a handful of json files where system-specific configuration can be stored in the user's home directory, allowing for easy version control of shared configuration. What killer configuration management feature do JetBrains' products offer that outweighs the aforementioned flaws?