|
|
|
|
|
|
| |
| Signed up: |
8 years ago (10/05/04)
|
|
|
Last signed in:
|
15 hours ago
|
| |
|
|
|
|
|
|
|
|
|
Programmers out there!This weekend I've been looking into PHP frameworks. Everyone raves about them, so I thought I might as well read through a bit of a documentation (I say a bit, really it's pages and pages and pages).
So far I've looked into CakePHP, Symfony, Laravel, Zend and Kohana. Whilst I like the idea of switching to MVC-based development (would make REST APIing easy) and URL routing is rather nice, I keep coming back to one issue in the back of my mind:
All these things are going to be bloated and slow as fuck.
Can anyone else who's worked with them offer an opinion? Over the years I've built my own toolset for things like encryption, cookie handling, input sanitisation, etc etc. I've already designed the wheel, so to speak, so switching to a framework doesn't really change anything for me. I think primarily what I'm searching for is a way to just switch to MVC, but surely I can do this super quickly by myself without the aid of a framework?
|
|
|
|
|
|
| |
|
|
|
Watch
Implementing existing website with cakePHP would be hard, and for such big website there could be a lot of optimisation issues. Just my opinion after using it for about 6 months.
As long as the interdependent code is clearly defined and divided, you can use jQuery to delegate the code's responsibilities accordingly. Then you can implement the code with something as simple as a CSS stylesheet, and use Ajax or cookies for persistence.
Whenever there's way like these to solve programming problems using easily writable code, I don't see any reason to use per-established frameworks.
As for specific frameworks, Zend and Symfony have been proven, by industry, to be strong frameworks for industrial use.
If you don't already read it, programmers.stackexchange.com has a lot more information on this topic, and will be able to give far better answers than the people of the Rooster Teeth community - fantastic as they are.
Your main issue with it would be deployment, since it takes a bit of work if you use Apache, but it's definitely possible.
Good luck learning it, though.
The framework designer found a way to do it, so why can't I find a way, that doesn't involve bloat/someone else's code to work with. So I would definitely recommend that you find your own way, relying on a framework might save time now, but it will suck later.
You mention the percentage of features used in the processing of a request being low meaning the overheads are not worth it. However, experience tells me that plenty of frameworks can be trimmed down to the essentials (core stuff and what you need) without any damage to functionality, speed or...
I think Ben will have quite a bit of work just determining the best c...
On the subject of MVC: I like MVC because the separation helps make a clearer distinction between what code does what job, and allows me to more easily reuse the same Model code across different Views. It also allows you to better make automated tests for your code to make sure when you change something, you don't break something else along the way.
As wikipedia will tell you MVC doesn't REQUIRE a framework, and you will be able to accomplish MVC methodologies without one, but it's possible a framework will accomplish what you want in cleaner ways than you would on your own.