genesis

You are correct that I also asked other online communities this question. I wouldn't say I was trying to force a narrative. I was asking out of concern. I was especially unnerved after seeing the development graph on GitHub: https://imgur.com/M09Nkx9 Also seeing there were features that haven't been implemented for the last 6 years made me even less confident about the future of the project: https://github.com/ziglang/zig/issues/68 Even from this post: https://andrewkelley.me/post/full-time-zig.html Of all the Zig projects the author said he was going to work on: - https://github.com/andrewrk/groovebasin/tree/zig - https://github.com/andrewrk/genesis/tree/zig - https://github.com/andrewrk/clashos he never committed and did any of them.

Thanks for this. Time to go fix my code[1]. [1]: https://github.com/andrewrk/genesis/blob/0d545d692110d33068d...

Building a free and open source multiplayer digital audio workstation. Here's the manifesto, copied from the README[1]: * Fast but not over-optimized. Waste no CPU cycles, but do not add unnecessary complexity for the sake of speed. * Take full advantage of multiple cores. * When there is a tradeoff between speed and memory, sacrifice memory. * Sample-accurate mixing. * Never require the user to restart the program * Let's get these things right the first time around: - Undo/redo - Ability to edit multiple projects at once. Mix and match - Support for N audio channels instead of hardcoded stereo * Tight integration with an online sample/project sharing service. Make it almost easier to save it open source than to save it privately * Multiplayer support. Each person can simultaneously edit different sections. * Backend decouple