The two parts are:
Perhaps it should have been obvious that Yahoo was seriously interested in Node. There's been a series of YUI Theater video presentations (linked below) starting with a video a year ago where Dav Glass gushed over and over and over about the game-changing power of being able to run YUI code on a server environment using Node. What that launched was a significantly large project to build a complete hosting platform which Yahoo could use to develop new web properties, and be opened to the public so non-Yahoo's could host applications on Yahoo's infrastructure.
The idea is to assemble a Mojit using a hybrid Node/YUI package structure, then deploy the tarball into Manhattan. Unfortunately I feel constrained in what I can say because Yahoo hasn't properly unveiled the product details yet, and at the time I left the team in June we were still in early stages of putting the platform together. Yahoo says that Manhattan is a cloud hosting platform, but in June … uh … Anyway, what I'll do is go over their blog posts today and see what I can expand upon.
Cocktails: Cocktails makes it simple to build, personalize and modify content for all consumer platforms, and to connect audiences with premium content.
Yahoo has a long history with an earlier platform for mobile applications, Blueprint, that detects device characteristics and customize the actual HTML or WAP code sent to the device based on the device grade. In part that knowledge is being applied to Mojito. Not that Blueprint is being used in Mojito. Instead they're re-applying that knowledge to Mojito.
Part of this is enabling the YUI library to run on either server or client. Manhattan is a hosting platform for Node, and while Node modules are excellent they're not quite compatible with being executed on a browser (client). They've published a few videos (linked below) about this idea, using YUI code in a Node module. Clearly for code to execute either on server or client it needs to use an API set that can run on either client or server. Because Node's API isn't compatible with running in the browser, this is where YUI comes into play.
Yahoo! Manhattan extends Node.JS to provide the necessary fault-isolation and fault-tolerance, scalability, availability, security and performance you’d otherwise expect from one of the largest web companies in the world.
That's a very information dense sentence because each word refers to whole areas of expertise which they poured into developing the hosting platform. This is the team I actually worked in, and I feel constrained from sharing too much. Basically what this means is a Mojito developer will not have full access to the entire Node API because of all these reasons. Additionally the vision is that the Manhattan infrastructure would spin up in a cloud-oriented fashion servers to handle traffic to each Mojit. Yahoo already has a world class web infrastructure which is providing some of the words mentioned in that sentence.
We will also make Mojito open source through YDN in the first quarter of 2012.
Later in 2012 we will be opening Yahoo! Manhattan for publishers to be able to run Mojito-based applications on Yahoo!’s Cloud.
Be patient ...
I wanted to close with embedding their videos in this blog post and talk about them. Unfortunately they're not allowing the videos to be embedded - so click on the "Shaken, Not Stirred" link below.
The first video shows Matt Taylor using the "mojito command line tool" to develop an application, then the "ghh" tool to deploy to a Manhattan server. Note the video doesn't show coding. The video demonstrates automatically degrading an application from a rich user interface down to buttons on an HTML page depending on the device characteristics. As mentioned earlier, they're intending to detect device characteristics and tune the user experience based on those characteristics. This is something Yahoo has years of experience from their mobile applications.
The video also shows the "ghh" tool - it's a command line tool for deploying applications to Manhattan. I'll be really surprised if ghh is delivered to the public for public use, because it didn't seem in June that ghh would ever be anything but an Yahoo-internal tool. But plans do have a way of changing as a project matures. I wonder if this is a video originally meant for internal training, that they trimmed down for this public showing?
The second video talks about solving the fragmentation problem that Yahoo saw. Yahoo has a long history of preferencing actual Web Standards rather than going for proprietary stuff. You can see this as a result of not owning the device of any customer hardware, and that therefore Yahoo's success depends on stressing open Web Standards.
A puzzle in the second video is what they mean by an "execution environment" in the browser for running Mojits. Clearly Node modules aren't directly applicable to a web browser because Node offers a lot of modules and API's that don't exist in browsers. Node modules are CommonJS modules (more or less) which can execute in a browser so I suppose that as long as your Mojit code doesn't use any Node-specific API's it could execute either on server or client.
Using Node.js and YUI 3 (Dav Glass in September 2010 gushing about YUI running in the server on Node)
Node.js Roadmap (Ryan Dahl presenting the Node roadmap at YUIConf 2010)
Node.js + YUI 3 (Dav Glass at YUIConf 2010)
YUI 3 and Node.js - Not Just For Web Pages (Dav Glass in May 2011)
Yahoo’s ‘Manhattan’ To Rescue Web From the iPad
Yahoo! Announces Cocktails – Shaken, Not Stirred
YUI for Cocktails