(from the post:)<p><pre><code> Second, now that I am no longer held back by big-company legal
restrictions, I am going to be much more involved with the platform.
Very soon I will post some new example code. Some others are
working on new documentation and build tools to ease that pain as well.
Starting this fall, my new company will also start to offer online and
in person training and mentoring courses to your team get up to speed
quickly. We can also finally get started in that book.
My goal is that by the end of the year, any average developer can pick
up SproutCore, build, and deploy a basic app without feeling lost. This
is open source and I can’t usually guarantee timelines but at least now
we can do what we need to make it happen.
</code></pre>
This is <i>very</i> welcome news. I had tried to start using SproutCore for a project earlier this year and ended up just using Rails with a more standard front-end because I already knew Rails, I was learning a few other technologies at the same time and SproutCore had very little documentation. If they can bridge that gap, I'm very very excited about where SproutCore could go.
Cappuccino vs Sproutcore. Preferences? Opinions? Experiences?<p>I've got an upcoming project for which I want to use one of those, and am leaning toward Cappuccino b/c it seems like more of a complete platform than a collection of cool widgets. But haven't had time to get my hands dirty with either yet, so maybe my first impression is wrong. Anyone used both yet?
This is incredible. You heard it here first - this is a direct competitor to Sencha. It was even mentioned in the post that licensing is not the way to go.<p>Charging to develop on a platform/within a framework is something that Apple and Microsoft do. Look at the proliferation of Java and Rails and I think you'll agree free, no-friction entry is the best way to go.