11–20 of 36 posts
Why not some form of user self-registration and admin management tool as well? I see a facebook connect in there, which helps, but a pure cake-based user reg/management system would go a long way towards a faster 'out of the box' experience.
Earlier quoted context omitted.
http://avnetlabs.com/php/php-framework-comparison-benchmarks
These benchmarks are from two years ago. The version of Cake used isn't even a stable release (1.2 RC1). Either way 1.3 has replaced 1.2 and is plenty fast for 99.99999% of sites.
Why not some form of user self-registration and admin management tool as well? I see a facebook connect in there, which helps, but a pure cake-based user reg/management system would go a long way towards a faster 'out of the box' experience.
CakePHP comes with that out of the box. You can use the built-in Auth component for registration and user management, and the "Bake" tools will give you the option of creating admin functions, similar to Django's.
Earlier quoted context omitted.
http://avnetlabs.com/php/php-framework-comparison-benchmarks
These benchmarks are from two years ago. The version of Cake used isn't even a stable release (1.2 RC1). Either way 1.3 has replaced 1.2 and is plenty fast for 99.99999% of sites.
Take with a grain of salt.
'fast' and 'CakePHP' shouldn't be used in the same sentence. Cake is great for RAD (Rapid Application Development) but the framework itself is massively bloated to almost the same level as a full CMS. You'll get to market faster, but you'll also be planning a rewrite or migration sooner should you enjoy some degree of success.
Most frameworks are bloated (not setup to REALLY scale) out of the gate.
CakePHP is very flexible, and if used correctly can scale for 99% of workloads. Especially if you leverage some of the php5 only nuances (cake 1.3 has been developed to support php4 and php5).
CakePlate can steer you in the right direction - but is not an end all. It helps turn your idea into reality quicker. If your idea twitter scales, then you have cash to throw at the (good) problem.
If you give Cake an honest shot, I'm confident you will like it.
'fast' and 'CakePHP' shouldn't be used in the same sentence. Cake is great for RAD (Rapid Application Development) but the framework itself is massively bloated to almost the same level as a full CMS. You'll get to market faster, but you'll also be planning a rewrite or migration sooner should you enjoy some degree of success.
agreed. i like codeigniter, which is an order of magnitude or two faster than cake.
Earlier quoted context omitted.
agreed. i like codeigniter, which is an order of magnitude or two faster than cake.
Consider Kohana, then, which forked off from CodeIgniter years ago and learned from the many mistakes CI made (most notably being a complete inability to adapt), and was designed with PHP 5 in mind from day one.
Why not some form of user self-registration and admin management tool as well? I see a facebook connect in there, which helps, but a pure cake-based user reg/management system would go a long way towards a faster 'out of the box' experience.
CakePHP comes with that out of the box. You can use the built-in Auth component for registration and user management, and the "Bake" tools will give you the option of creating admin functions, similar to Django's.
Earlier quoted context omitted.
These benchmarks are from two years ago. The version of Cake used isn't even a stable release (1.2 RC1). Either way 1.3 has replaced 1.2 and is plenty fast for 99.99999% of sites.
Here's a more recent benchmark: http://symfony-reloaded.org/fast
Earlier quoted context omitted.
agreed. i like codeigniter, which is an order of magnitude or two faster than cake.
Consider Kohana, then, which forked off from CodeIgniter years ago and learned from the many mistakes CI made (most notably being a complete inability to adapt), and was designed with PHP 5 in mind from day one.