Find solution
how can I integrate slim framework in cakephp?

What are the pros and cons of using Django (web framework) to code the front end of a site versus a home grown PHP (programming language) framework or CakePHP?

  • Answer:

    Full disclosure: I'm a big fan of django so my views might be biased. Pros:   Organization - Django has a pretty clear MVC (Model/View/Control) layout. The request also has a clear path through urlresolvers, middleware, view and context processors. It's just clean   ORM - Thinking and writing in it's Object-Relational Mapping is nice. Queries are lazily executed. Interesting things can be done with memcached queries etc. Models are pulled as instances of your model class. And if you can't do something the django way, there's usually a workaround.   Python - Python > PHP. You can research this more yourself. Slightly subjective but in my experience Python is vastly more writable and readable than PHP.   Customizable - You can swap out your DB, your Template Framework, and your ORM. Cons:   Additional overhead - It's certainly "fast enough" and can certainly be made to be "super fast" by removing un-needed features etc. Really not an issue at all. But I had to put *something* in the cons list...

Nesan Waran at Quora Visit the source

Was this solution helpful to you?

Other answers

If you have a lot of experience in programming and frameworks, rolling your own is always a good idea. You get exactly what you need, and the tool you know best is the tool you built yourself. The drawbacks include that it takes a LOT of extra time, and you'll have to train programmers in your framework, as there is 0% chance they know your custom framework. If you built something on Django, you can advertise for Django programmers. Python is just a much more well-maintained language than PHP and much more well designed. As everyone, I'm biased, and you need to do the research yourself, but really, for me it's a no-brainer. You might want to check out the answers to As for CakePHP, it's not a bad framework per se, but one could argue that it's really just a clone of Rails for people that don't want to learn Ruby. It's a good choice if you know PHP very well and need to build a site like right bloody now (the best code almost always comes out of using what you know well) but from a purely technical standpoint, Rails and Django are ahead, as they don't have the baggage of PHP to carry.

Mattias Petter Johansson

Related Q & A:

Just Added Q & A:

Find solution

For every problem there is a solution! Proved by Solucija.

  • Got an issue and looking for advice?

  • Ask Solucija to search every corner of the Web for help.

  • Get workable solutions and helpful tips in a moment.

Just ask Solucija about an issue you face and immediately get a list of ready solutions, answers and tips from other Internet users. We always provide the most suitable and complete answer to your question at the top, along with a few good alternatives below.