money and skilled programmers to write some of the tightest, fastest, most
optimized code around if they wanted to. The extra few dollars to make the
code 'fast but inflexibility' (it really isn't inflexible, it's just
specific to the needs of the MM site) is worth it to avoid what started this
entire thread. To have anyone see an error on a website, let alone for there
to be an error in the first place is just not acceptable (in my mind when
thinking of a multi-million dollar internet software company).
> 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]
