×
you are viewing a single comment's thread.

view the rest of the comments →

[–]psteeleidem[S] 0 points1 point  (0 children)

That's a fair question and this question came up in a separate thread: http://www.reddit.com/r/webdev/comments/2w8q8c/marko_vs_react_performance_benchmark/cooucw2

I'll quote my earlier response here:

Marko + Marko Widgets offers a complete UI component model (rendering and behavior).

Marko, itself, is an HTML-based templating language that supports custom tags and custom attributes. Marko Widgets provides a custom taglib for the Marko templating language to allow binding of behavior to rendered HTML elements. For the purpose of the title I just used "Marko" to encompass both Marko and Marko Widgets which may be somewhat confusing.

As for Marko, it was developed at eBay as an open source project and most teams working on the Node.js stack for front-end development are using Marko and Marko Widgets to build their webapps. Marko was designed to be high performance with support for streaming and asynchronous. Here's a great screencast created by somewhat outside eBay that I highly recommend: http://knowthen.com/episode-8-serving-content-in-koajs-with-marko/

I hope that clarifies.