@publickeating So after all that, did you not read the posts, or just choose to ignore the actual issues that where brought up?
did you have something to say about how we'll handle useStaticLayout with the 2 different view types?
I guess,will this even be an issue? The view could detect if a template has been given, and set useStaticLayout: NO.
How about the fact that template views go against the design principals allowing an interface builder?
Also yes, the Ember guys have left us, but unfortunately their legacy hasn't. The very fact we have 'core_view' (plus the whole 'modularising' of SC) was from their first attempt at making SC 2, before choosing to start anew. What Erich is saying, is many of these changes where made without regard for performance of large apps. This is something that we need to take into consideration for each and every change we make. While you might not have a vision for where you want SC to go, many of us do. It's why most have chosen SC, and that vision is a framework that runs fast even when the apps are big, over changes that make it easier to write (not that they have to be mutually exclusive).
So, no this may not apply to this particular proposal of yours, but there does need to be a guiding ideal behind any framework, otherwise it gets overrun by mediocracy.