Motorola's Montage Javascript app framework | Hacker News Reader

Motorola's Montage Javascript app framework

github.com

34 pointsfarski16 comments

Is this a downstream result of work done by the 280 North team? Meanwhile, Github "Issue count" = 280, heh.

I thought the same but I asked one of the core dev's and he wasn't even familiar with Atlas. So, no.

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 :)

Two questions:

1) Another full stack JS Framework? What makes this special?

2) What interest does Motorola have in JS Frameworks?

A few of the things we think makes Montage special are

* 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

The kitchen sink example required authorization. How does one get credentials?

Thanks, we're looking into it and it should be fixed soon

edit: now working http://tetsubo.org/mot/montage/examples/sink/

Why should people use it over other frameworks like AngularJS?

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.

The logger does not work, at least on the Kitchen Sink page.

I've just tested it and it seems to work fine. Clicking a button in the button example logs a message to the logger at the bottom of the screen.

Is it wrong that when I see the term data binding I have bad flashbacks of Silverlight/WPF development?

What is wrong with data binding? I only know the basics of it but I find it pretty useful. Is there something I am missing?

There are purists that would insist that data binding is always less efficient than writing your own bare metal approach.

Largely, they are right. But the time invested in doing so could often be spent elsewhere, while your data-bound forms work "just fine".

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!?!

It loaded quickly for me, despite the poor network here.

Reply on news.ycombinator.com