> The problem with every framework that exists is that it has to be
> generalized. It is almost totally non-specific because it has to be
> used on site A, site B, etc. This leads to code that may work but is
> not the tightest, fastest or even the most optimized for the site. MM
> should be going the tight, optimized, elegant code route. Instead
> they're going the 'mass production' route. They should be beyond that
> point.
There is almost always a trade-off between flexibility, abstraction,
etc. and performance, but one typically tries to strike the right
balance between the two extremes. The right balance typically falls
between the cost of extending and maintaining a fast but inflexibility
application, and the cost of having to throw hardware or other
optimizations as a slow but highly configurable application. I'm
certain Sean's team understands this equation and has made their
decisions accordingly.
Christian
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
