(topher) Build system (this is one thing I've found really frustrating with Angular; there are so many options you don't know which one to choose)

I'd love to see this get even stronger/easier with 2.0 (using node is of particular importance I think)

(topher) Relatively easy to make custom views (although we've said we want this to be even better/easier)

(maurits) State system

(maurits) built in store system to deal with large amounts of data / records

(tyler) You can build a large percentage of an app using SproutCore's features (i.e. you don't need to custom develop or bring in very much)

in particular, anything custom developed in a project is usually pretty poor Deadlines, hacks, whatever, I've rarely found custom implementations to be on par with an SC framework view

(tyler) touching the DOM as little as possible

(maurits) OO system (object oriented)

(topher) View customization/placement: I mean, it's hard to create views because the layout/positioning/padding is done in JS, but padding can also be done in CSS (and everything else usually is) which makes it hard to know the right way to do something. I can't count the number of times I wanted to fix a list view to add some padding between items, but couldn't get it working properly.

(maurits) it is currently rather easy to make endless loops with observers, which especially for beginners can be boggling

(topher) relatively small number of views/components (when compared with some current frameworks)

(tyler) that's one that I'd like to solve more of. I have so many views 90% done waiting to bring in

(maurits) no table view

(topher) Currently, mobile support is not really considered (although I don't think we're too far off from having something pretty fantastic)

(maurits) not at all far off, I am using SC on mobile, in Cordova, a pleasure

(topher) getting started - difficult to get up-and-running; documentation is still a bit lacking