Marko
Marko

8
12
38
React
React

25.4K
17.3K
3.4K
Add tool

Marko vs React: What are the differences?

Developers describe Marko as "An isomorphic UI framework similar to Vue". Marko is a really fast and lightweight HTML-based templating engine that compiles templates to readable Node.js-compatible JavaScript modules, and it works on the server and in the browser. It supports streaming, async rendering and custom tags. On the other hand, React is detailed as "A JavaScript library for building user interfaces". Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.

Marko and React can be primarily classified as "Javascript UI Libraries" tools.

"No JSX" is the primary reason why developers consider Marko over the competitors, whereas "Components" was stated as the key factor in picking React.

Marko and React are both open source tools. React with 132K GitHub stars and 24.5K forks on GitHub appears to be more popular than Marko with 9.08K GitHub stars and 565 GitHub forks.

What is Marko?

Marko is a really fast and lightweight HTML-based templating engine that compiles templates to readable Node.js-compatible JavaScript modules, and it works on the server and in the browser. It supports streaming, async rendering and custom tags.

What is React?

Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.

Want advice about which of these to choose?Ask the StackShare community!

Why do developers choose Marko?
Why do developers choose React?

Sign up to add, upvote and see more prosMake informed product decisions

What are the cons of using Marko?
What are the cons of using React?
What companies use Marko?
What companies use React?

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Marko?
What tools integrate with React?
    No integrations found

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Marko and React?
    jQuery
    jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML.
    jQuery UI
    Whether you're building highly interactive web applications or you just need to add a date picker to a form control, jQuery UI is the perfect choice.
    AngularJS
    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.
    Vue.js
    Vue.js is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API.
    Prototype
    Prototype is a JavaScript framework that aims to ease development of dynamic web applications. It offers a familiar class-style OO framework, extensive Ajax support, higher-order programming constructs, and easy DOM manipulation.
    See all alternatives
    Decisions about Marko and React
    No stack decisions found
    Interest over time
    Reviews of Marko and React
    Review ofReactReact

    Perfect workflow

    How developers use Marko and React
    Avatar of Instacart
    Instacart uses ReactReact

    Before two weeks ago or so, it used to be Backbone views and models, and everything was on our main store app, and our mobile web app, but actually, we just switched our mobile web app to using ReactJS for the interface. So it’s using Backbone models but ReactJS front-end components. Really, it was borne out of the frustration with how the Backbone model-view bindings worked, and it wasn’t especially performant for large views, and we had to do lots of tricks to make it performant. But swapping that out with React views meant that it could be both simpler and faster without having to spend a lot of time on that.

    One other interesting thing about that is, since React actually works okay with the Backbone models and the Backbone router and stuff like that, we didn’t have to rewrite the mobile web application and update it to ReactJS. Rewrites are almost always a bad idea. We were able to upgrade pieces of it at a time, move on to React, and now the entire thing is using React and just has the Backbone router and models and stuff like that that we already had, so it's a lot faster.

    Avatar of Netflix
    Netflix uses ReactReact

    At the beginning of last year, Netflix UI engineers embarked on several ambitious projects to dramatically transform the user experience on our desktop and mobile platforms. Given a UI redesign of a scale similar to that undergone by TVs and game consoles, it was essential for us to re-evaluate our existing UI technology stack and to determine whether to explore new solutions. Do we have the right building blocks to create best-in-class single-page web applications? And what specific problems are we looking to solve? Much of our existing front-end infrastructure consists of hand-rolled components optimized for the current website and iOS application. Our decision to adopt React was influenced by a number of factors, most notably: 1) startup speed, 2) runtime performance, and 3) modularity.

    React has exceeded our requirements and enabled us to build a tremendous foundation on which to innovate the Netflix experience.

    Avatar of Cloudcraft
    Cloudcraft uses ReactReact

    Web-frontend programming prior to React: like banging rocks together. With React: Like wearing fusion powered underwear. Gives you a nice warm feeling. Using React for Cloudcraft.co allowed us to create a beautiful UI in record time (1 month start to launch), with virtually no bugs popping up during development. The functional approach to just rendering your component given a state just makes so much sense, with React figuring out the delta between your current and desired representation. It's the future kids!

    Avatar of Kurzor, s.r.o.
    Kurzor, s.r.o. uses ReactReact

    React is choice number 1 when it comes to JS development at Kurzor. We choose React because it solves many issues with web applications in a elegant way. Writing an app in components is useful for coordination and isolation of concerns. React forces you to abandon state and use vertical passing through props instead. And having as many Pure Components as possible helps to write cleaner code.

    With React we usually use: Redux, React Router, React Toolbox, Styled Components.

    Avatar of Kent Steiner
    Kent Steiner uses ReactReact

    This is the best component framework and API available today for building modern web sites and apps. I really enjoy how minimal it is, and powerful at the same time. It removes opinionated development and replaces it with logic and data philosophies, which has in turn fostered a robust and lively code and support community.

    How much does Marko cost?
    How much does React cost?
    Pricing unavailable
    Pricing unavailable
    News about Marko
    More news