Make a comparison table with Loco

[m4tx]

Not sure if this should be here, or on the website, but it would be useful for potential users to compare Cot with Loco (and potentially other "batteries-included" frameworks, including non-Rust ones such as Django or Rails).

[mandarvaze]

@m4tx if you create a placeholder page with "Coming soon", I can attempt to update the page with differences.
We can iteratively improve it.

Also, I think this issue belongs to https://github.com/cot-rs/cot-site

[m4tx]

@mandarvaze fair enough, I've transferred the issue to cot-site.

I've created a placeholder page in 3f7c3e3. Any help with this issue will be appreciated!

[jondot]

Loco author here, hello @m4tx
I'll be happy to help with the comparison table.

But first, did you try Loco? what didn't you like that made you start a Django-like project? (Django was historically part of a publishing shop and so is highly item-based, more like CRM that evolved into an app framework).

[m4tx]

@jondot The reason for starting Cot was a bit more prosaic: the idea was born even before Loco had its first commit. Even though I actually started working on Cot much later, I discovered Loco's existence halfway through the development, so any dissatisfaction with Loco wasn't the reason to build Cot; it was rather the dissatisfaction with the old state of things.

I ultimately decided to carry on with the development anyway due to some design decisions that I wanted to make that were different from Loco's. While Loco tries to stick quite strongly to the projects it is built on, mostly providing the glue code between them (correct me if I'm wrong), Cot tries to provide hopefully nicer APIs by integrating much deeper into the libraries. For example, we don't use any fancy features from axum (we even want to switch to using hyper because of that); instead, we build APIs that are much better integrated with the rest of the framework. Similarly, our ORM is based on SeaORM's internal query-building library but provides nicer APIs and integration with our admin panel and automatic migration generator. We're not trying to rebuild everything, but instead, we are identifying places where the users may strongly benefit from rebuilding components to provide a much more integrated experience. There are more differences obviously, but I think that was the main one.

Best of luck with Loco anyway. Hopefully, both projects can ultimately benefit from each other in a truly open-source spirit!

[jondot]

That's an interesting route to go into!, I hope to see how it evolves and somehow cooperate :)
If you need any help/pointers in the comparison just tag me with '@' and I'll jump in.