Re:A marketing guy's guide to Getting Technical
by mikk0j on Tuesday May 29, 2012 @09:31AM
(#4037347)
Thanks. This is partly why I made the point of there being good comments to that post - I can see there are plenty of differing opinions on this, and I'm can't say what is right. But, for a newbie to thinking about program structure (well, at least for me) presenting that with clear borders is helpful. But I think you're right, calling it MVC is not helpful. What should the HTML/CSS/browser bucketing be called instead?
Re:A marketing guy's guide to Getting Technical
by troels on Tuesday May 29, 2012 @10:16AM
(#4037551)
Theoretically, it's not a bad point of view, but for a newbie, it's not how the concept "MVC" is normally used. I would suggest linking to something like this: http://guides.rubyonrails.org/getting_started.html#the-mvc-a... - Now, Rails isn't the only way to do MVC, but it's more or less the de-facto standard, so it's good for understanding the basic concepts.
I don't think it makes sense to consider HTML-CSS-JS as a triad on par with MVC anyway. CSS and HTML are very intimately related, so I think it makes most sense to consider them two parts of one technology. JS is more separated and generally takes different skills than HTML/CSS.
Re:A marketing guy's guide to Getting Technical
by mikk0j on Tuesday May 29, 2012 @10:41AM
(#4037660)
Great, thanks, this is now addressed in an edit in the post. Also good point on making a separation based on skills.
http://www.codinghorror.com/blog/2008/05/understanding-model...
This dude says MVC == HTML, CSS, 'the browser', respectively. Not sure many would agree with that assessment. If anything those three could, I suppose, be viewed as a separation of concerns, calling it MVC however, just seems muddy.
For example the way I see the pattern in terms of web apps (and MVC is not a domain specific pattern in any respect either):
- model should be largely in code and data and contain the business logic, not HTML.
- view is a mixture of HTML/CSS
- control is a mixture of the browser engine's logic and client side javascript.
Also Github and .NET don't seem to fit well together based on the types of communities. ;) That's not to say they can't in the future, just speaking historically.