{1166} - 1.3.1 Benefits
Why use MVC? Because it is a tried and true software design pattern that turns an application into a maintainable, modular, rapidly developed package. Crafting application tasks into separate models, views, and controllers makes your application very light on its feet. New features are easily added, and new faces on old features are a snap. The modular and separate design also allows developers and designers to work simultaneously, including the ability to rapidly prototype. Separation also allows developers to make changes in one part of the application without affecting others.
If you've never built an application this way, it takes some getting used to, but we're confident that once you've built your first application using CakePHP, you won't want to do it any other way.
{3836} - 1.3.1 Benefits
Why use MVC? Because it is a tried and true software design pattern that turns an application into a maintainable, modular, rapidly developed package. Crafting application tasks into separate models, views, and controllers makes your application very light on its feet. New features are easily added, and new faces on old features are a snap. The modular and separate design also allows developers and designers to work simultaneously, including the ability to rapidly prototype. Separation also allows developers to make changes in one part of the application without affecting others.
If you've never built an application this way, it takes some time getting used to, but we're confident that once you've built your first application using CakePHP, you won't want to do it any other way.
Differences
| Lines: 1-3 | Lines: 1-3 | ||
| <title>Benefits</title> | <title>Benefits</title> | ||
| <p>Why use MVC? Because it is a tried and true software design pattern that turns an application into a maintainable, modular, rapidly developed package. Crafting application tasks into separate models, views, and controllers makes your application very light on its feet. New features are easily added, and new faces on old features are a snap. The modular and separate design also allows developers and designers to work simultaneously, including the ability to rapidly <a href="http://en.wikipedia.org/wiki/Software_prototyping" title="What is software prototyping?">prototype</a>. Separation also allows developers to make changes in one part of the application without affecting others.</p> | <p>Why use MVC? Because it is a tried and true software design pattern that turns an application into a maintainable, modular, rapidly developed package. Crafting application tasks into separate models, views, and controllers makes your application very light on its feet. New features are easily added, and new faces on old features are a snap. The modular and separate design also allows developers and designers to work simultaneously, including the ability to rapidly <a href="http://en.wikipedia.org/wiki/Software_prototyping" title="What is software prototyping?">prototype</a>. Separation also allows developers to make changes in one part of the application without affecting others.</p> | ||
| - | <p>If you've never built an application this way, it takes some getting used to, but we're confident that once you've built your first application using CakePHP, you won't want to do it any other way.</p> | + | <p>If you've never built an application this way, it takes some time getting used to, but we're confident that once you've built your first application using CakePHP, you won't want to do it any other way.</p> |
