about 1 year
ago
CakePHP:
Realistic, comprehensive framework
by
Giuliano
Pros:
-Fully featured. Lets you do 80% of what you want out of the box and always gives a clean way of doing the other 20%
-Fast development. Abstracting SQL is a tough task but these guys have really done a great job. Add the containable class and you will need to maybe write 1% of your queries manually.
-Organized. MVC is one of the best ways to separate logic, db, and html.
-Proven to work. Many frameworks will sound great on
... [More]
paper but will not be able to accomplish real world scenarios. This framework has been used to create many different types of websites and has been built from those needs.
Cons:
-Documentation
-1.2 isnt GA yet (but it will be soon)
-It takes a little bit to get good at it but once you do, you won't go back. [Less]
1 of 5 users found the following review helpful.
Was this review helpful to you?
Yes
|
No
about 1 year
ago
Grails:
Still has a long way to go
by
Giuliano
I recently had the opportunity of working with Grails. It sounded great on paper like any of the other MVC frameworks. However, there are a few key problems which make Grails a very unpleasant technology to work with.
1. The biggest problem is definitely the lack of support for advanced features, specially in queries. If you want to do any kind of advanced querying then you will be writing SQL code. The framework simplifies SQL to an
... [More]
unrealistic point. If you are using associations (something so basic) then good luck doing any kind of advanced filtering, sorting, etc... with the built in tools.
2. Debugging is a mess. If you have an error during your bootstrap or other start up problems then good luck if you can even read the stacktrace in your command prompt (They have over 500 calls in the stacktrace). I had to pipe mine out to a file then read the file in notepad.
If your bug is in your controller/view then you get a nice webpage with the exception. The only problem is that the error message on the website is 95% not your actual problem. It will tell you the problem is on line 150 while the problem is most likely down another 50 lines.
3. The documentation is poor. I used Grails to do a semi-advanced project and outside of the basics, the documentation will not get you far. I found myself often searching on google for answers and through trial and error.
4. Memory consumption and performance. Grails is a memory hog. My website when doing absolutely nothing consumes nearly 80 megs. One of the main problems that may increase your memory consumption and/or CPU is because of problem #1 on this list. You will so often be doing advanced things manually that should be done by the database and/or the framework. Many times I had to duplicate/triplicate objects to accomplish what I needed.
5. Buggy. The framework randomly throws Hibernate errors (concurrent session problems etc..) when I am browsing my website. You refresh the page and the problem goes away.
All in all this is one of those frameworks that have a lot of potential but it is simply not ready to be used for any real world scenarios. It has obviously not been used for many website applications because it lacks way too many basic tools. I would recommend RoR, CakePHP, Zend, Symfony, or Django over Grails to anyone. [Less]
3 of 11 users found the following review helpful.
Was this review helpful to you?
Yes
|
No
