fantasma_oskar I think this is an interesting opinion. However, one thing I would like to add is that when exporting in JSON or binary format, unless you are packing textures, even with a large number of skeletons in a single Spine project, it will not take that long to export.
I tested duplicating the mix-and-match skeleton, which is one of our sample skeletons, which is one of our sample skeletons, having 15 skeletons in a Spine project, exporting the skeleton data without texture packs, and measuring the time with a stopwatch, and the result was 1.83 seconds.
The export of the atlas can be done by running the texture packer separately, and depending on the input folder path specified, it is possible to perform a pack for each image used in the skeleton, so if you are currently exporting skeleton data and packing textures at the same time, you may want to do it separately to save time.
Also, if you are currently exporting from the editor UI, you may want to consider doing so via the CLI. This will allow you to run the export on a separate instance of the editor without having to stop working on the currently running editor. See this blog post for more information:
https://esotericsoftware.com/blog/New-export-shell-scripts
I hope this information is helpful.
