It might be bad practice to dump 1.3GB of variable user data into the registry, though. Especially when there's SQL servers and Nuget packages that can deal with that kind of data in a platform-agnostic way.
Seems like horrible dev practice to place save data of any kind in the Windows registry lmao. I get that it's designed for storing user data in some respects but the registry is an old and fickle solution to setting global variables important for communication between processes and applications.
If you're storing data that's only ever needed by your own application, especially if it isn't OS-related, you shouldn't mess with the registry. Not only does it not have the performance you'd expect for most circumstances, but the registry has a real performance and stability impact even when outside of your app.
What's worse, imo, is that this data is difficult to access for making backups, utilising cloud synchronization, and cross compatibility of your app.
Unity is a lot more borked than I thought, but KSP devs should probably be careful with what data serialisation APIs they mess with.
As a Unity dev of 6 years, playerPreffs (the unity system that stores data in the registry) are a good place to store small amounts of data in a dictionary style structure quickly without creating your own data system. But they are extremely limited in the types of data they can hold and the control a dev has over them. Whenever I see playerPreffs used I think the dev must-have needed something quick and easy. They may have also created their own registry save system in that case should be an easy fix. (De)Serializing json or even custom binary files in compartmented files in a defined folder like StreamingAssets gives much more flexibility in data types and control.
You can see playerPreffs limitations in the documentation below:
(https://docs.unity3d.com/ScriptReference/PlayerPrefs.html)
Basically a network/local/user specific configuration database. Playing with it can break apps that expect their config to be in it, or to be of the type expected, even though they shouldn’t.
This about:config on Firefox but system wide. It’s your ~/.config and /etc/ folders in one database format, also manageable with AD and proper permissions.
Is It a frontend for dconf? I have to admit I never tinkered with any dconf stuff before as I live mostly in terminal and web browsers. Does dconf share similarities with windows registry?