Hi HN, others and I have been working on this inside Motorola and can answer any questions you have. You can also join us on irc://irc.freenode.net:6667/#montage :)
Interesting. What scenarios are you specifically targetting for Montage to excel in? e.g. mobile? touch? I noticed that you target Safari and Chrome. Does this mean it is more suited to an enterprise environment rather than consumer environment - where people may run Opera, MSIE etc?
Why is Motorola releasing this? What kind of risk that it will not be supported and the platform left to wither?
How does Montage compare with Knockout.js? The latter is more incremental, and seems to be a safer choice.
Is it just me or are all the examples slow as balls. I thought there was a js rendering error or something, but no, the kitchen sink took 30 seconds to load!?!
16 comments
[ 2.8 ms ] story [ 47.5 ms ] thread1) Another full stack JS Framework? What makes this special?
2) What interest does Motorola have in JS Frameworks?
* very fast, realtime, two way, object to object bindings (non DOM based)
* reusable components built using regular HTML, where markup and behavior are completely separated (see the .reel directories under ui/)
* based on CommonJS, with complete script dependency loading
Edit:samples now up at http://tetsubo.org/docs/montage/samples/
We are also developing an HTML5 and Montage authoring tool, built using Montage: https://github.com/Motorola-Mobility/ninja
edit: now working http://tetsubo.org/mot/montage/examples/sink/
Why is Motorola releasing this? What kind of risk that it will not be supported and the platform left to wither?
How does Montage compare with Knockout.js? The latter is more incremental, and seems to be a safer choice.
Largely, they are right. But the time invested in doing so could often be spent elsewhere, while your data-bound forms work "just fine".