>  [stacy] There's a big difference between you and an average developer
>  getting up to speed on grunt work in a web app though. ;)
>
I don't believe the average developer is below being able to quickly
get up to speed on an application.

>  [stacy] Again, most likely a result from a well crafted design on your
>  part. That requires a level of expertise not available in many
>  organizations.
>
That may be, but I believe that is where frameworks come into play. The
idea is to use the best framework for the application in question. If
you aren't capable of determining that then using an existing framework
from someone else is likely the way to go. However, that doesn't
invalidate the notion that "homegrown" frameworks are any harder to
understand or be productive in than frameworks with a community behind
them.

>  [stacy] I'd agree some applications require a specific/custom/extended
>  framework but many can fare quite well in commonly available
> frameworks.
>
Require and benefit mean two different things. It may be that many
application don't require custom frameworks, but it also may be that
they can benefit from them.

-Matt
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to