Hacker News Reader

About JS MVC frameworks - It's about scaling your development teams by putting a re-usable pattern in place so that things will jell together.

HTML5 - My point was, understand the parts you can use now.

Optimization - Again, do it when you are ready to do it.

View on HN

You can scale development teams and put re-usable patterns in place without pushing all your templates and view logic to the client. That's what libraries like Backbone are made to do, and I would agree it is generally overkill to implement a site that way.

Was talking about leveraging a suitable, existing library that follows a MV* pattern, not about creating your mygreatnextjsmv*.

About implementation - definitely depends on use cases. Anyway, learning them won't hurt anyway.

> About JS MVC frameworks - It's about scaling your development teams by putting a re-usable pattern in place so that things will jell together.

But is MVC the right pattern all the time? I really doubt it.

Reply on news.ycombinator.com