React vs Krita

Since every single UI component is created independently in JavaScript, it becomes very easy to reuse them throughout your app without having to re-write them.

React is built by Facebook engineers initially to be used only for their inner projects especially to solve the problem of building large complex applications with constantly changing data.

React can render it's components and data server side, then it sends those components as HTML to the browser.

This ensures faster initial loading time and SEO friendliness out of the box, since it's indexed as any other static website by search engines.

Instead of relying on the DOM, React implements a virtual DOM from scratch, allowing it to calculate precisely what needs to be patched during the next screen refresh. This is orders of magnitude faster than fiddling with the DOM itself.

React's one-way data binding (or one-way data flow) means that it's easy to see where and how your UI is updated and where you need to make changes. It's also very easy to keep everything modular, fast and well-organized.

ReactJS can be used independently as the only library for building the front-end, or it can be used alongside JavaScript libraries such as jQuery, or even Angular.

React provides a template engine (JSX) which is easy to use. But it's not mandatory.

The framework is widely used in the industry.

Since React's virtual DOM system is implemented completely in JavaScript, it's very easy to write UI test cases.

React has an official Chrome Extension which is used as a developing and debugging tool. It can be used to quickly and painlessly debug your application or view the whole application structure as it's rendered.

Flux is a platform agnostic pattern which can technically be used with any application or programming language.

One of Flux' main features is that it enforces uni-directional data flow which means that views do not change the data directly.

With React this is useful because this way it's easier to understand an application as it starts getting more complicated. By having two-way data binding, lead to unpredictable changes, where changing one model's data would end up updating another model. By using the Flux architecture, this can be avoided.

Since React v0.15, SVG is fully supported. React supports all SVG attributes that are recognized by today's browsers.

React is just a view library, so you still have (almost) full control over how your app behaves.

Reagent, Om, Rum, etc.

React is used on one of the most visited websites on the planet, Facebook. With stellar results and with millions of people experiencing it every day.

All the most used and useful tools are easy to find in Krita's UI and are often just one click away. They are not hidden behind menus or dropdowns.

Krita is getting constant releases with updates and bug fixes. New features are added at a pace that far surpasses the other alternatives.

Krita is completely free and open source. They have raised a couple of successful Kickstarters in the past to get the initial financing and now they are accepting donations.

KDE has a long history of making solid applications.

Krita's preset brushes are one of the default dockers. Each brush has a preview on mouseover that shows a detailed view of the type of brush involved. All the brushes also have useful and descriptive names such as "HP Pencil" or "Textured Fuzzy".

Although the UI is rather busy, Krita is very customizable. The editing window can be themed and the sidebar can be customized extensively throw many dockers or panes.

Tiled view that shows your image tiled in the editor, and permits you to edit it as you are seeing it tiled. If the brush passes out of your texture, it will just automatically wrap back the painting to the other side of the original texture, while permitting you to paint and see the results on any of the tiled "clones" (the shortcut key to activate this is w by default).