Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comparison with react-intl #303

Closed
oyeanuj opened this issue Sep 26, 2017 · 3 comments
Closed

Comparison with react-intl #303

oyeanuj opened this issue Sep 26, 2017 · 3 comments

Comments

@oyeanuj
Copy link

oyeanuj commented Sep 26, 2017

Hi folks! Thank you for putting out this library. Since the library tagline mentions 'i18n done right', I was wondering if you could provide a brief comparison (pros/cons/tradeoffs) between this library and react-intl (and/or some other prominent react i8n solutions)?

I'm sure it would be super helpful to others as well, who are in the same boat trying to make s decision.

@jamuhl
Copy link
Member

jamuhl commented Sep 27, 2017

Hm...comparison is hard - as the maintainer of i18next i'm too deep into i18next to make a fair comparison i think: i once made a medium article showing some benefits of i18next over formatjs in general and polyglot: https://medium.com/@jamuhl/i18n-frameworks-the-unfair-showdown-8d436cd6f470

Pro for sure is i18next is not react exclusive - you learn it once and can use it in future in any framework (and believe me react will go some day too ;)) -> https://www.i18next.com/supported-frameworks.html

Further with v6 you can use not only hocs but render props too -> https://react.i18next.com/getting-started.html#basic-sample-using-render-props

vs HOC & Provider: https://react.i18next.com/getting-started.html#basic-sample-using-hoc

Hm than there is the video showing the line behind i18n -> localization -> the process not only instrumentation: https://www.youtube.com/watch?v=9NOzJhgmyQE

Inline components can be translated very easy: https://react.i18next.com/components/trans-component.html

Tradeoffs:

  • JSON format - No icu format (which in my view is a matter of taste - i think icu format is bloated and very complicated to use - takes to much time for developers to format right - while most cases you just need simple interpolations
  • Not baked by ex-yahoo (not sure how they maintain that now): but still i18next ecosystem is over 6 years old

Ideas / Help on how to highlight the pros / cons of react-i18next in comparison to react-intl would be awesome (but i always fear to sound biased)

@oyeanuj
Copy link
Author

oyeanuj commented Sep 27, 2017

@jamuhl Thank you for the detailed response, appreciate it. I'll go over it all, before I ask more questions!

@jamuhl
Copy link
Member

jamuhl commented Oct 1, 2017

Closing for now...feel free to reach out again if having more questions....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants