and developers are easy to please in regards to performance. Users
and clients on the other hand, are not. This is true in any framework
(or lack there of). Performance matters, why develop in such a
wonderful framework if its frustrating for the end user? (Twitter
comes to mind with ROR).
CakePHP is a developers framework, true, its inherently going to be
slower than pure HTML etc; indeed. What has me shaking my head is
looking at all the other frameworks going from 1.x to 2.x increasing
their performance with each major release whereas we've gone backwards
at a 1:2 (1:4 in linked Yii Benchmark) rate with something as simple
as pages per second of static (or near static) content.
I admit I'm new to CakePHP, and I will reiterate how impressed I am
with the framework as a whole. I was seduced by Cake by its ease of
use and console/bake feature which I've grown to love. I'm moving
away from ROR because of performance issues and cost.
I just don't want that to be a trend is all, because I love to bake
and eat cake oh so much. *smile*
On Jan 2, 11:21 am, Mathew <nfoscar...@yahoo.com> wrote:
> > For most people making such apps the speed of the dispatcher, template
> > engine etc is unimportant. The parts slowing the app would be heavy
> > SQL, SOAP/XML-RPC-request to other apps or huge batch ETLs. For most
> > people (including most public websites) the most important thing would
> > be faster SQL/active records and a better implementation of HABTM
> > joins, not the ability to serve x or y pages per sec.
>
> Very well put.
>
> Cake is a developers framework.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to cake-php+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
No comments:
Post a Comment