Hello, my name is Dmitry Karlovsky and I ... practice thermorectal aromatherapy. I understand that everyone loves their swamp and will protect it to the last drop of liquid. However, a high engineering culture requires objectivity in evaluating tools.

Often, there is more than one option that suits the functionality of the solution to the same problem. Other things being equal, I would like to choose a project that will cause the least problems. But how to estimate the volume of these problems offhand without spending a few man-years for filling all kinds of bumps with your own hands?

Well, let's look at what problems there are, how to evaluate them and compare some popular projects.

Problems

Errors in the code

Nobody wants a tool that is buggy or just doesn't work. They usually have an issue with the tag "bug".

Rake in architecture

The architecture may not be tailored to the way you want to use it. Moreover, sometimes the architecture is useless, even in seemingly basic use cases. Issue in this case, if they start, is lengthy in the spirit of "how to do this?" or "why doesn't it work as I expect it to?"

Documentation

If the documentation is incomplete, not up to date or not at all, then mastering the tool will be fraught with difficulties. An issue is usually raised on it with the "documentation" tag.

Imperfection

If a feature is not implemented very conveniently or is not implemented at all, then you have to write your own facades, decorators, adapters and other proxies in order to adapt the tool to the realities of your project. They usually have an issue with the tag "improvement".

Support

. , , . . . , , , , . Issue . .

, , issue — , , , . , issue, . , .

, , . . , , . , . , , .

, , . issue, . , ...

TypeScript FlowJS?

— Haxe. . .

React Angular?

Angular , , . , . . .

Redux MobX?

MobX . issue, , . , , .

RXJS . , , . RxMarbles .

MomentJS Luxon?

, date-fns. .

, , , , , . , , , (, AngularJS, , Polymer, , GWT, , GCT). - , .

, , , , . - , . . — , .

, " ", " " " , ". , , -.

My comparison tool is available at compare.github.hyoo.ru . Keep in mind that it uses the github API from your IP, and it has pretty tight limits. So if the github starts pouring 403 errors, you can either wait a bit or change the IP via VPN.

Attach screenshots of your favorite projects and analysis of why the results are exactly the same and not different. Improvements and bug reports are welcome as usual.