2. Aerospace has significant performance issues with workspaces. The problem has persisted for over a year, and there are no plans to fix it. That's why I started building FlashSpace - to make it blazingly fast. Which limitation is especially interesting to you? FlashSpace addresses the animation lag, the number of workspaces is unlimited, and you can move apps between workspaces with hot keys.
3. FlashSpace already supports JSON config files which are stored by default in ~/.config/flashspace, so you can easily sync them.
Thanks for your response! Regarding question 2, I think my initial understanding of FlashSpace was that it was using the macOS spaces API, which has been known to have its limitations (as documented in the Aerospace docs I shared). Now that I've played around with FlashSpace, I believe it's not using that API. So I think I'm clear on the questions.
I really like how FlashSpace plays well with macOS native tabs. One follow-up question I had is how you manage your windows? FlashSpace not managing windows on one hand is really nice for floating windows (e.g., mpv), but in your examples you have all the windows already set up with some gaps around each. Is all that set-up done by dragging windows around with your mouse? I use an accordion layout heavily, and I don't see how I can make it work with FlashSpace.
In the video, I think they were manually dragged. But I also use Rectangle Pro for moving windows around with simple shortcuts (many apps have this feature, another one is Raycast). I don't use tiling managers though. Most of the time they cause too many problems and glitches.
1. Does FlashSpace require disabling SIP?
2. Aerospace documents the limitations of macOS spaces [1]. How does FlashSpace deal with these limitations?
3. Do you have any plans to support file-based configuration? I like syncing my dotfiles between multiple computers.
[1]: https://nikitabobko.github.io/AeroSpace/guide#emulation-of-v...