<p><pre><code>  &gt;  I&#x27;ve done a bit of ember, and it seems heavy to me, 
</code></pre>
One thing about Ember: it&#x27;s specifically for &quot;ambitious&quot; applications. The idea is that you&#x27;re going to be building something which needs all those things, so it&#x27;s better to have them in the framework, where best practices can be shared across projects. Once you&#x27;ve built out those features yourself, you&#x27;ve built a custom framework anyway.<p>An interesting point about frameworks, generally: they have a constant overhead. So for smaller projects, the framework dominates the application, but as the application grows, the application will dominate the framework.