Posted almost 3 years ago. Visible to the public. Repeats. Linked content.
Choosing the right gems for your project
Adding a gem means you take over the liability towards the external code.
Checklist
Based on "To gem, or not to gem":
- Gem is really needed (prefer writing your own code for simple requirements without many edge cases)
- Gem is tested well (coverage and quality)
- Gem has a good code quality
- Gem's licence fits to the project requirement
- Try to avoid gems that do much more than your requirement scope needs
- Gem has a good maturity and maintenance
- Gem has a good / familiar DSL
- If it's hard to do right, choose a mature gem (e.g. Devise or Clearance for authentication) instead of building it yourself
Also see the chapter "Owning your Stack" in the book Growing Rails Applications in Practice.
Services
Does your version of Ruby on Rails still receive security updates?
Rails LTS provides security patches for old versions of Ruby on Rails (3.2 and 2.3).
