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

Replace the gem mobility instead of globalize #1446

Open
tyranja opened this issue Feb 23, 2025 · 0 comments
Open

Replace the gem mobility instead of globalize #1446

tyranja opened this issue Feb 23, 2025 · 0 comments

Comments

@tyranja
Copy link
Member

tyranja commented Feb 23, 2025

πŸ”Ή Mobility (More Flexible & Modern)
βœ… Pros:

βœ” Actively maintained & modern (recommended for new projects).
βœ” Supports multiple backends (you can store translations in JSON, a separate table, or even key-value stores).
βœ” Better performance (if using JSON or key-value store instead of joins).
βœ” Works well with APIs & modern Rails versions.
❌ Cons:

βœ– Slightly more complex setup than Globalize.
βœ– Some features require extra configuration (e.g., using fallbacks properly).

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

1 participant