Cappuccino - The Node.js Project

&#62; <i>The original build system used ant, which was then followed by rake, which ran on Ruby. In 2010 the build system was ported to JavaScript and jake (a port of rake), which ran on top of narwhal (a CommonJS runtime) and the package manager tusk. This is the system we are still using today.</i><p>Sigh. No prizes for guessing what will happen in two years' time when node.js is no longer the shiny new hotness.

uhm, grunt? <a href="http://gruntjs.com/" rel="nofollow">http://gruntjs.com/</a> It's exactly a "brand-new build system — reimagined from the ground up — that leverages all of the power of node, npm and their thriving ecosystems". I use it on several projects and it works really well. It's probably my favorite build system across all languages for its simplicity, extensibility, and utility.

You could run the existing Narwhal code on Node.js using Common Node: <a href="http://olegp.github.com/common-node/" rel="nofollow">http://olegp.github.com/common-node/</a><p>The library implements most CommonJS proposals on top of Node.js using node-fibers making it possible to run RingoJS and Narwhal code on Node as is. I'm using it in production on <a href="https://starthq.com/" rel="nofollow">https://starthq.com/</a>.

Anyone using Cappucino in production? Looks pretty awesome, although a bit slow I found, but not really heard of too many people using it.

Does anyone knows what happened to their cool cappuccino dot org domain?

Whatever happened to Atlas? I thought cappuccino was dead.<p>It seemed clear to me that it needed an Interface Builder equivalent, but Atlas was in perpetual beta and ignored for years, motorola bought them and the 280 north guys went to "hot" startups.<p>I was really interested in Cappuccino for quite awhile, still would be if it could deliver a working system that was in reasonably good shape. (I'm not saying it can't, but it's apparently being abandoned years ago made me believe I shouldn't invest time into it.)