3 ms·
Has anyone who also used SproutCore have any thoughts on how they stack up? SproutCore also stabilized into 1.0 recently it seems.
by papersmith 17y ago
Has anyone who also used SproutCore have any thoughts on how they stack up? SproutCore also stabilized into 1.0 recently it seems.
- boucher 17y agoWorth noting we aren't calling ourselves 1.0 yet. This is just our one year anniversary. Also worth noting that SproutCore 1.0 is still in beta, and almost a complete rewrite, rather than a stabilization of what was already there.
- sandofsky 17y agoI developed a few toy projects to learn each framework. Cappuccino is an incredible technical accomplishment. I've done iPhone development, and it's true that you can easily map your Cocoa experience onto Cappuccino. However, when I hit a corner case such as embedding a SWF, the abstraction leak was a nightmare. Sproutcore feels safer because it doesn't hide the fact you're working with HTML/CSS; you need to write it to create custom views. Inserting a SWF was straightforward. The other reason I favor Sproutcore is the feeling Cappuccino has cargo cult issues. For example, Sproutcore uses namespaces while Cappuccino just prefixes initials. In Sproutcore you have "SC.Object" while Cappuccino uses "CPObject." Cappuccino is still pre 1.0, so all of this could change, but if I had to choose a framework to write an app today, I'd go with Sproutcore.
- boucher 17y agoI'm not sure what "cargo cult issues" are, but Cappuccino uses prefixed globals because they are strictly faster than using "namespaces" (which really aren't namespaces). It makes a big difference in IE.
- catch23 17y agounless things have changed recently, SC's 1.0 beta is anything but stable. It's great for hobby projects, but I would worry if attempting to use it for production. I guess if you're starting a new project now, SC isn't a bad route. Will probably be stable soon.