> Ditch Enyo. No more messing around with your own frameworks and stuff. Writing them is fun, but web developers don’t want to learn yet another framework. The framework wars are over, and jQuery is the winner.
jQuery is not a framework...
I agree generally but I don't think he takes it far enough. If Enyo is just a js framework like Cappuccino or Backbone.js then the first thing they have to do is open source Enyo. I should be able to run an Enyo app on iOS or Android or Fennec or whatever.
Next they need to drop their packaging mechanism and embrace Open Web Apps[1].
Next they need to allow non-Enyo js apps to be packaged and installed as "native" apps.
Doing these things would put WebOS on footing with other competitor "web oses", specifically ChromeOS and Boot to Gecko. Except that WebOS would have beaten them to the punch on having a mobile UI perfect for multitasking web apps.
Re:Steps to save webOS
by jackson71 on Thursday August 25, 2011 @10:13AM
(#2924942)
You can already use jQuery, and you can package non-Enyo apps to submit and install as "native" already. A good number of both webOS 1.x, 2.x, and 3.x apps do this because of the familiarity.
jQuery is not a framework...
I agree generally but I don't think he takes it far enough. If Enyo is just a js framework like Cappuccino or Backbone.js then the first thing they have to do is open source Enyo. I should be able to run an Enyo app on iOS or Android or Fennec or whatever.
Next they need to drop their packaging mechanism and embrace Open Web Apps[1].
Next they need to allow non-Enyo js apps to be packaged and installed as "native" apps.
Doing these things would put WebOS on footing with other competitor "web oses", specifically ChromeOS and Boot to Gecko. Except that WebOS would have beaten them to the punch on having a mobile UI perfect for multitasking web apps.
[1]https://apps.mozillalabs.com/