Skip to content
This repository has been archived by the owner on Oct 30, 2018. It is now read-only.

Testimonials

Jump to bottom
Joe Catera edited this page Sep 25, 2013 · 9 revisions

After two or three weeks, with Django as backend and jQuery as frontend, I replaced Django with Mojito (which is based on Node.js & YUI) and jQuery with YUI because - except for one Django-specific reason (db-layer) - it has a huge benefit: ONE Language & ONE Framework on Client & Server. I think this is a unique property of YUI.

Source: Is there any particular reason why YUI isn't popular?

I am an Intern from BITS Pilani working with Yahoo Games Team. (...) Now the situation has changed with lot more precise Mojito documentation which is available on the Internet. One of my friend has learned this technology in 7 days after it was open sourced on GitHub. I would like to thank the Yahoo team for delivering this awesome technology which is scalable, does device specific presentation, uses MVC and is really fast. It's lot more fun doing application development in this technology.

Source: Sanket Tulangekar, internal communication

Mojito is a great choice for enterprise customers building software that must be deployed across many devices/locales/channel/servers/etc. Basically, if you want a solid MVC framework to build software for planetary-wide distribution, this is an viable option. You need to be willing to drink the full cup of YUI Koolaid!

Source: John Engstrom, NodeJS Google Group

You know what would be awesome? If we wrote our libraries so that they could run either on the server or on the client, and they did so in a transparent way. (...) Imagine a framework where the first page-load was always rendered server-side, meaning the client gets a single fully-rendered page. Then for desktop browsers, browsing around the site just made calls to API endpoints returning JSON or XML, and the client rendered the templates for the changed portions of the page. For mobile browsers with less power or for search engines, the rendering would always be done on the server. Imagine that the templating library could record some key metrics to determine how long things were taking to render, and dynamically switch between rendering on the server and client based on server load or client speed.

Source: Why Node.js disappoints me by Eric Florenzano. (While not a testament of usage, Eric exemplifies the kind of thinking that led to Mojito.)

Clone this wiki locally