5 ms·
Author of Chandler here. While rewriting the project is extremely fun and definitely a very good learning curve for us, we actually care A LOT about our users.
by robinhood 4y ago
Author of Chandler here.
While rewriting the project is extremely fun and definitely a very good learning curve for us, we actually care A LOT about our users.
I believe Chandler is much, much better to use than the current crappy Monica. It's easier, better UI and UX wise, and have way better features. And we are working our asses off to provide an API, and an importer to let you import your data so you won't lose anything.
I agree, while we are rewriting the software, we don't have time to do anything on the current codebase, except bug fixes here and there. It's a price we have to pay unfortunately.
So why do we rewrite? It's simple - the current codebase is old, and complex, and not fun to work on. We have merged things in the codebase from the community that we shouldn't have merge. The DB structure is old fashioned, and not flexible, so migrations would be a nightmare to do. I'm not saying it's not possible to improve the current codebase, but... that would be an actual job, and we don't want it to feel like a job.
- Shank 4y ago> We have merged things in the codebase from the community that we shouldn't have merge. Do you have examples of what these features are/were? And, sort of tangentially, do you recommend actually setting up Monica in 2022 or waiting until Chandler to try the stack?