5 ms·
This is of course a function of when you tried it. Its been out for over a year now, and in that time we've built out support for a lot of the built in widgets,
by tolmasky 17y ago
This is of course a function of when you tried it. Its been out for over a year now, and in that time we've built out support for a lot of the built in widgets, especially for our 0.8 release. Things like TableView work very well now (which last time I checked is a class that isn't even that well supported in SC at all). And again, the proof is ultimately in the pudding: most of the apps that are shipping today have used either nib2cib or Atlas, and we have very few users who don't begin development today straight from our nib2cib based projects.
- devinus 17y agoFair enough. I tried to keep my criticism firmly in the past tense too, because I wasn't sure how much love nib2cib has had since I evaluated it.
- ynniv 17y agoThe choice between SproutCore and Cappuccino is largely philosophical (port something that works, or build fresh with new perspective), and based on limited data. The way I see it, either choice is still a choice for a client side web framework, and that's a step in the right direction. For instance, Narwhal/CommonJS/SeedJS came out of these efforts, and benefit all involved.