You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love Vue, I really do, but lately I've been playing with React, because I moved to having my backend interface as graphql, relay style and the relay client is for React only.
After getting some used to, React isn't so bad (and React only, Next is a nightmare), but i18n in the React ecosystem is awful.
Vue-i18n is simple and practical.
And when migrating from vue to react or back, having the same data structures for translation files would be very benefitial.
So having a core i18n lib with wrappers from vue, react, svelte, angular,... would be a great thing to have.
Each ecosystem has its own little soup. Why not have the same soup in every kitchen?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I love Vue, I really do, but lately I've been playing with React, because I moved to having my backend interface as graphql, relay style and the relay client is for React only.
After getting some used to, React isn't so bad (and React only, Next is a nightmare), but i18n in the React ecosystem is awful.
Vue-i18n is simple and practical.
And when migrating from vue to react or back, having the same data structures for translation files would be very benefitial.
So having a core i18n lib with wrappers from vue, react, svelte, angular,... would be a great thing to have.
Each ecosystem has its own little soup. Why not have the same soup in every kitchen?
Beta Was this translation helpful? Give feedback.
All reactions