3 ms·

I genuinely think any new JS web application framework needs to answer several key questions on the front page, above the fold - for starters: - How is this d

I genuinely think any new JS web application framework needs to answer several key questions on the front page, above the fold - for starters: - How is this different to Backbone.js/underscore.js, Spine.js, Sproutcore, etc.? - Who's using it? (I realise the list will be short for new projects) - Why should I learn a new framework when my other tools seem to be working just fine? - What are its dependencies, and what templating libraries does it use/support? There are probably more (chime in if you have any!) but if you can answer these without resorting to impressive demos or long lists of (expected) features, I'd consider trying it out for a low-risk project and hope it saves me some time/hassle...

rolux 14y ago
Hey, thanks for your feedback. You're reading introductory blurb v0.1, so there's definitely room for improvement. To answer your questions: - The core library (Ox.js) is somewhat similar to underscore, while the UI module (Ox.UI) is more like YUI or Ext JS. Unlike backbone, OxJS comes with actual widgets, and it doesn't suggest a strict MVC model. Even though you may end up writing code that follows the MVC paradigm rather closely. - So far, the only major project using OxJS is pan.do/ra (https://pan.do/ra https://pan.do/ra). But then, OxJS has just been made public. - In case the tools you're currently using give you the right abstractions and objects to build big applications (like pan.do/ra), then my suggestion would be to stick with them. Maybe try out OxJS for a small side project. - Ox.UI wraps jQuery, but other than that, there are no dependencies. You can bring any third-party templating library, but the idea is that you won't need one. The UI widgets are your "views", and that's it.
wilmoore 14y ago
Other questions one might answer: - Were other libraries (YUI3, Backbone, Ember, ...) evaluated and if so, what were their weaknesses and how does this improve on that? - What are the core strengths of the framework?

rolux 14y ago

Hey, thanks for your feedback. You're reading introductory blurb v0.1, so there's definitely room for improvement. To answer your questions: - The core library (Ox.js) is somewhat similar to underscore, while the UI module (Ox.UI) is more like YUI or Ext JS. Unlike backbone, OxJS comes with actual widgets, and it doesn't suggest a strict MVC model. Even though you may end up writing code that follows the MVC paradigm rather closely. - So far, the only major project using OxJS is pan.do/ra (https://pan.do/ra https://pan.do/ra). But then, OxJS has just been made public. - In case the tools you're currently using give you the right abstractions and objects to build big applications (like pan.do/ra), then my suggestion would be to stick with them. Maybe try out OxJS for a small side project. - Ox.UI wraps jQuery, but other than that, there are no dependencies. You can bring any third-party templating library, but the idea is that you won't need one. The UI widgets are your "views", and that's it.

wilmoore 14y ago

Other questions one might answer: - Were other libraries (YUI3, Backbone, Ember, ...) evaluated and if so, what were their weaknesses and how does this improve on that? - What are the core strengths of the framework?