I'm still considering reasons for or against this change. I think it would help with scalability.
Each time you save a launcher, the entire launcher configuration for all launchers is re-saved. This is a fast operation, but if you have a lot of launchers it could start to slow down.
One file per launcher would mean that saving could be a per-launcher operation--no other launcher files would need to be touched when saving one. Steam and Epic do this with their respective game manifest files. Smaller platforms like Blizzard do not do this, but there is a finite number of games you can have in those smaller platforms.
It could also help facilitate syncing and sharing per-launcher if the entire file didn't have to be re-processed.
Additionally, when you save a launcher, the launcher config needs to be re-loaded. Perhaps if it were per-launcher, only that one launcher's config could be reloaded.
I'm still considering reasons for or against this change. I think it would help with scalability.
Each time you save a launcher, the entire launcher configuration for all launchers is re-saved. This is a fast operation, but if you have a lot of launchers it could start to slow down.
One file per launcher would mean that saving could be a per-launcher operation--no other launcher files would need to be touched when saving one. Steam and Epic do this with their respective game manifest files. Smaller platforms like Blizzard do not do this, but there is a finite number of games you can have in those smaller platforms.
It could also help facilitate syncing and sharing per-launcher if the entire file didn't have to be re-processed.
Additionally, when you save a launcher, the launcher config needs to be re-loaded. Perhaps if it were per-launcher, only that one launcher's config could be reloaded.