The vision of Kumiko

[No767]

Kumiko started off as a fork of Rin. The idea was to have Rin be the main bot, while Kumiko was just set up as an experiment. Later on, I slowly and slowly dropped support for Rin due to burnout, and boredom of doing the same things over and over again. I shifted my attention to Kumiko, and started to develop most the features. As of now, Kumiko's codebase is an absolute dumpster fire; a collection of the stuff I learned on while working on Rin. From working on Xelt and Akari, I learned a ton of new things, including migrating back to discord.py v2 when originally Danny archived the project. Even though Pycord is undergoing a major reconstruction with their v3 version, it would seem like more work to migrate to Pycord v3 than to migrate back into discord.py v2. In the process of programming Kumiko, I've overcomplicated a lot of the internals, and migrated from SQLAlchemy to Tortoise ORM and now to Prisma. It seems like the more I go down this rabbit hole, the less productive I feel while working on Kumiko. In order to speed the process up, I've created a roadmap (#266) to attempt to note what are the things that needs to be done, and the goal of Kumiko. At the end of the day, Kumiko was built to be unique, not to copy from others

Basically this means a ton of the old backend code and features will be stripped and replaced with more modern code and utilities. And if you haven't caught the gist, Kumiko will be undergoing another full major rewrite