The acronym MVC is confusing and bad for teaching Rails

[lilliealbert]

Thinking about ripping all mentions of MVC out of Suggestotron and replacing with an explanation of the request cycle that starts with the router. I think that MVC is nice shorthand for people talking about that particular architecture pattern, and super duper confusing for new folks — even just the order, "Model, View, Controller", is confusing.

Opinions?

[rachelfenn]

Steven pulled out the diagram and explanation and put it into another
small document, with the intent of having it be in a reference section
as well as in Suggestotron. It is possible that just having it in a
reference section is good enough. If people don't need to know about it
to do Suggestotron, then it might be good to just leave it as "suggested
reading". Or we could put it into a curriculum that goes in-between the
Curriculum and the Intermediate Curriculum.

By the way, having the curriculum named Curriculum is a little confusing
once we have more than one of them...

-r-

On 10/23/2013 9:10 AM, Lillie Chilen wrote:

Thinking about ripping all mentions of MVC out of Suggestotron and
replacing with an explanation of the request cycle that starts with
the router. I think that MVC is nice shorthand for people talking
about that particular architecture pattern, and super duper confusing
for new folks — even just the order, "Model, View, Controller", is
confusing.

Opinions?

—
Reply to this email directly or view it on GitHub
#259.

[alexch]

On Oct 23, 2013, at 9:10 AM, Lillie Chilen notifications@github.com wrote:

Thinking about ripping all mentions of MVC out of Suggestotron and replacing with an explanation of the request cycle that starts with the router. I think that MVC is nice shorthand for people talking about that particular architecture pattern, and super duper confusing for new folks — even just the order, "Model, View, Controller", is confusing.

Opinions?

I agree but aren't we stuck with it? Rails uses those names for its layers and that acronym for its architecture and its all over the web now.

I suppose we could call it "Rails Architecture" instead, and just mention models and views and controllers (and routes) as needed.

And yes, the Curriculum curriculum is silly and I'd be fine renaming it to Rails Intro or similar.

• A

[lilliealbert]

I get that it's all over the place, but especially for the brand new people, MVC becomes this capital-T Thing that is confusing. "Rails architecture" sounds super nice.

(It's still on this page: http://docs.railsbridge.org/curriculum/creating_a_migration, at the bottom.)