Hacker News Reader

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?

View on HN

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.

Great, thanks, this is now addressed in an edit in the post. Also good point on making a separation based on skills.

Pleasure. As for your question, hmm not sure, but I suspect SoC (Separation of Concerns), fits the closest.

http://en.wikipedia.org/wiki/Separation_of_concerns

Reply on news.ycombinator.com