QCUBED Versus CAKE!!! Please Help!
Tue, 05/12/2009 - 14:40
HEEEEEEEEEEEEEEELP!
My boss is about to phase out development with Qcube in favour of CakePHP. He just feels it time to stop Qcoding and start Baking...lol
I, on the other hand feels like I need to continue with Qcodo. He won't switch if I can convince him. Now that's where you people come in. I have little experience and most of you here have years upon years of experience. Please, can you give me a NON-BIASED comparism of both frameworks so I can speak well on the D-Day (Decision Day) and its gonna be anytime soon. Please. Thanks People, I love you all! :)
This ancient thread will help you: http://www.qcodo.com/forums/topic.php/253/1//?strSearch=cake.
Biggest difference in my mind: code generation (qcodo/qcubed) versus runtime reflection (cake, etc). Resulting performance difference are quite significant - qcubed is dramatically faster, plus, it offers type hints at coding time.
Yeah, thanks Alex, i'ld sure digest this tonight and see for myself but meanwhile, we had arguments about how possible it is for Qcubed to support very large scale enterprise projects like Workflow Management, Collaboration, CRMs, etc. What do you have to say about that?
QCubed's QForms have a small issue with overhead, where they require some additional CPU and memory compared to some other frameworks. There is an open ticket to address this.
That said, on the development side things are significantly easier to code, and the performance of the application will largely be based on your business logic and coding, rather than framework performance. How much you cache, use expands, etc make a huge difference.
We used QCubed to build an enterprise Learning management System used by dozens of very large (including fortune 500) companies, and have had no issues with the framework performance itself. (Though we have had areas where optomizations of our usage were clearly needed.)
An enormous deployment of QCodo/QCubed is the chess.com website - you can imagine the overhead of having to support concurrent connections / synchronization of multiple simultaneous games...
I have use QCodo for many projects. I am in the middle of writing a collaboration program now. I like the code that it generates, and having the ability to use QQueries for object oriented SQL querying.
CakePHP is really nice, I love the gimmicks and marketing they use. (Baked sites, cookbook documentation, etc) It makes everything seem so simple and kid friendly.
Both platforms are going to have up sides and down sides, or we wouldn't be needing to choose. I think after we start hammering away on QCubed 1.1 and have the file structure cleaned up and some better plugins for codegen and qforms, then we will have CakePHP beat because we will have a more simplified end user experience and also have the power of generated classes (models) from the database.