1. Somebody should wake up and take RIM's lunch, not Apple's. Build a thin candy bar webOS device with an excellent keyboard and a decently sized screen. Palm went all in on the Pre form factor instead of Pixi, which I maintain was their biggest mistake to date.
2. Deliver on the webOS promise to developers. Mojo wasn't it. Surprisingly, Enyo is! My hat is off to the Enyo guys.
"Just use jQuery" is the new "just use RegEx." I loooove jQuery, but it doesn't really help you in managing a huge application. There is a reason why people use backbone.js, knockout.js, javascriptmvc, and the like, in addition to jQuery.
Enyo lets you assemble your apps from components. I'd be the first to say that my bs meter went live when I heard that. 99% of the time, "its modular" is an empty promise. However, for version one, Enyo is bang on. I'll be honest though, the thought "another fucking framework..." _has_ crossed my mind in frustration.
Yet, I am staring at my webOS mobile app running in Chrome right now -- inspector working and all -- and it's like staring into the future. _This_ is the way mobile apps are meant to be built. _This_ was the promise.
This brings me back to the article re: packaging. I package this enyo app in a second's time and it's up running the same code on the device or emulator, and it all feels native to the OS. As long as the code is the same, I don't care if you package it in a cup cake.
Enyo is actually a very good idea. All they have to do is give it an appropriate, free to use without restriction, license.