Cappuccino 0.9 (opens in new tab)

We're definitely still here, but the newer guys have really stepped up for this release so they deserve to be highlighted. I think that's a great sign for the long term viability of the project. If 280 North were hit by a bus Cappuccino would no longer die, which it probably would have 2 years ago.

I will tell you, as someone who drafted the blog post, we chose to highlight the newest members of our team rather than putting the original founders name on everything we publish. The community is growing very quickly.

Also, Ross's name is in the blog post. If you take a look at the Github repo you can see that both Francisco and Tom have recently put a lot of work into this release as well.

I think you have only to look at the commit authors to see that it's pretty evenly spread out amongst all of us which is a great thing in my opinion

Who says we aren't still team members? We just didn't help write the blog post.

Well, GWT still deals heavily with HTML, CSS, and the DOM. It does offer certain abstractions that many frameworks do not. Both projects are certainly targeting a similar (but not completely identical) market.

I'm not quite sure what you mean by "the real contender" though.

Cappuccino and Objective-J will certainly be extremely comfortable for those coming from a Cocoa or GNUStep background. But even for traditional web developers, Objective-J allows you to do some extremely powerful things that just wouldn't be possible otherwise. That said, it is still a strict superset of Javascript, so any valid Javascript is still valid Objective-J, and vice versa.

You can read more about it here: http://cappuccino.org/discuss/2008/12/08/on-leaky-abstractio...

While I don't think that making Mac developers feel comfortable was the Cappuccino team's primary motivation, the knowledge reuse that this enables is one tremendous advantage.

Developers well versed in Mac development have years of accreted knowlege of design patterns, common mistakes, and best practices, a great swath of which apply also to Cappuccino development.

I'm not talking about trivial things like how buttons clicks trigger functionality, or how to show a dialog; those can be learned in a short time in just about any language/framework.

I mean things such as: how to do robust undo/redo involving complex object graphs, how to build performant UIs that manipulate tens or hundreds of thousands of data records, or how to design complex interfaces with dozens of windows and model-view-conroller sets that avoid tight coupling and remain reasonable to refactor and maintain over time.

Building up this type of knowledge really does tend to take months, if not years, in just about any development environment you care to name. So the fact that Cappuccino leverages the experience that you or your team already has--in addition to doing the work of providing a framework and toolkit for UI and app logic, and abstracting away the DOM--is a tremendous advantage.

This is true only for some people, obviously; it's not a benefit if you don't already have that kind of experience (although IMO cap should still be on your short list of things to evaluate for new web apps). But if you do have significant Mac development experience, and especially if you're working on a short 8 or 12 month development cycle (say some company's internal HR admin app, or something like that), it can be the difference between hitting your deadline or being months late because of an accumulation of unforeseen issues and learning experiences along the way.

So I, for one, am heartily thankful to the Cappuccino team.

As was previously mentioned, Objective-J is a strict superset of JavaScript, which means it only adds things. Basically, we took features that are repeatedly added by other JS libraries (and that we believe are really better served as language features) and made them language features. A good example of this is classical inheritance. Just about every JS framework or library implements classical inheritance in one way or another using functions. We believe its much more intuitive to just have a keyword. For a really in depth explanation of our thinking, check out this blog post:

http://cappuccino.org/discuss/2008/12/08/on-leaky-abstractio...

My experience of Objective-J is that is really makes writing large applications in (essentially) Javascript manageable. It's a fantastic asset.

Got a whole page of projects here:

https://github.com/280north/cappuccino/wiki/Current-Projects

A fairly recent impressive Cappuccino application is PicsEngine:

http://www.picsengine.com/

Also check out GitHub Issues which very nicely demonstrates the state of the art TableView widget:

http://githubissues.heroku.com/

Archipel is more of a technical app highlighting a ton of various '2.0' techs in one app unified by the Cappuccino experience:

http://archipelproject.org/

Cappuccino is used on a variety of projects, some are internal and some are not. I've listed several applications being powered by Cappuccino, but certainly there are many more if anyone wants to list them.

- http://picsengine.com/home

- http://gomockingbird.com/

- http://enstore.com/

- http://280slides.com

- http://githubissues.heroku.com

- http://timetableapp.com/

- http://almost.at/

There's a pretty good list of some of the public apps here: http://cappuccino.org/learn/demos/