In the back of your head, though, you have a question. And its an important question. Actually, damn it, you have more than one question, but I don't know who ate the last slice of cheesecake or why it isn't lunch time yet. I'm here to answer a different quetion:Do you care about Cappuccino?
Why, yes, you do. That isn't to say that you'll ever use Cappuccino. You probably won't, but you do care.
Why You Care
Cappuccino not only encourages, but demands API-centered development.由于大多数应用程序逻辑被处理了客户端，因此您的服务器只需要实现一个简单的API，用于为无法处理客户端的应用程序的有限方面服务。
Also, this API-centric approach supports developing applications on multiple platforms. The API could support a Cappuccino application as well as an iPhone application. Flexibility is a好thing.
Cappuccino promotes code reuse.By making it easier to separate code into multiple files--and making traditional OO inheritance easy to take advantage of--Cappuccino makes it easier to design reusable swathes of code.
角度280Northcreators have focused on in Cappuccino is thatCappuccino allows bypassing CSS and HTML cross-browser hell.This is an important asset, but personally I don't consider it to be themostcompelling benefit.
Managing cross-platform issues is frustrating, but as more designers and companies begin to ignore IE6, the process is becoming signifigantly less burdensome.Cappuccino is about the future, and cross-platform issues are part of the receeding past, so focusing on them too heavily seems a diservice to Cappuccino's appeals.
There are a number of compelling reasons to use Cappuccino, but nonethless I suspect that most developers will never come in contact with it (beyond some experimention in their personal time).
The biggest reason you'll never use Cappuccino is because它与其他人正在使用的太不同。这是Lisps从未在主流中捕获的主要原因之一，最后我怀疑它会阻止卡布奇诺从利基到普通的利基交叉。
One of the side-affects of modeling Cappuccino after a desktop application toolkit is thatfunctionality is cheap, but presentation is expensive。For its sundry problems, HTML and CSS are masterful at displaying content, and desktop applications generally have a much simpler approach to displaying content.
With the high standards for design on the web, cheap functionality can only go so far, most projects require cheap presentation as well.
HTML and CSS are the lingua franca of the web, and many existing services provide their data in them. BecauseCappuccino doesn't speak the lingua franca fluently, it is less able to reuse existing code and less able to interoperate with existing services (although it handles JSON quite well, so services which are data--but not formatted data--heavy will interoperate nicely).
就像我告诉过你的那样，你会关心卡布奇诺。这是令人兴奋的，它将在未来几个月和多年来激发一些CopyCat项目。这些项目是否进入主流使用可能取决于他们与现有的HTML / CSS基础架构共存的能力。
Along that route exists a balance between ease of functionality and ease of presentation, and potent new avenues of web development.