React.JS Localization v0.2

Remember my last post about React.js localization? Not 2 years passed yet and I’m happy to share with you the “proper” way to do localization in React.js. Globalize.js Yes, I still use globalize. As I said in my previous post, the Common Locale Data Repository is maintained by Unicode Consortium and have support for every possible locale. Please don’t re-invent the wheel. Languages are hard (believe me, I know Russian) and I’ve seen a lot of people trying to do their own localization and plurals.
7 min read

The land of undocument react.js: The Context

Русская версия на Хабре. Перевод не мой, спасибо webMarshal-у за перевод. If you have any questions, or want to discuss some points — leave a comment here, or tweet me. If we take a look at React component we can outline some properties. State Yes, each react component has state. State is something internal to the component. Only the component it self can read and write into its own state and as the name implies, the state of the component is used to store state (captain obvious here).
8 min read

A different approach for localizing react.js app

Howdy! I’ve heard you use ReactJS? Good! I also heard you want to localize your application? That’s great! Well proper localization is hard, there are many js libraries for client side localization as well as yahoo/react-intl that provides localized react components based on JavaScript Intl API. I my self use es6 syntax and avoid using mixins, because mixins are dead (and well, because there is no easy way to integrate mixins into es6 syntax).
6 min read