Ways to evaluate a gem

Experienced coders shared their thoughts about finding the perfect gem
21 June 2017   2786

Sometimes every coder faces with hard-solving issues. One “little” problem can provide you with headache and sleepless nights, spent on forums and web, searching for a solution. When you face a problem or difficulty, try to “look around”. There is a big chance that someone had already found a solution and you don’t have to “invent the wheel” again.

Ruby

A dynamic, open source programming language with a focus on simplicity and productivity.

Ruby on Rails

Ruby on Rails (RoR) - a framework written in the Ruby programming language.

Luckily, Ruby and RoR has a strong, friendly and open community. There is large amount of ready-made gems, so, there is high probability to find the right one.

We’ve collected a list of advises from skilled developers, how to choose a right gem.

  1. Look through Readme file and try to understand what is written there. Joking aside, it’s really hard sometimes.
  2. Look at the number of stars and watches. Big and active community keeps project healthy. Large amount of users means that finding help will be much easier. Also, a collective mind is a great guide. But it is not smart to consider only this criterion.
  3. Date of last update shows how active the project is. But regular updates for simple code aren’t necessary, so, this criterion isn’t the main.
  4. Take a good look on project’s issues. Check, is it filled with bug reports or new add-ons, are there any active discussions, are they structured. Also, don't forget to check how many pull requests are closed.
  5. Look thru the forum posts and bug tickets of a specific gem do decide, are the maintainers act helpful? You have to decide, can you count on them if any big issues arise.
  6. Take a good look at the number dependencies. A “simple” gem can have a large number of dependencies. You should decide if you are able to put all of them into your project. Also, note that there's a risk of version conflict.
  7. Don' forget to look at official documentation. It is necessary for every serious project. Also, it has to be understandable and contain “real-life” examples.
  8. Check the code. Are you able to understand it? If something goes wrong, maybe you will have to rewrite some parts of it by yourself. And it's better for you to be able to do it.

Ruby/RoR News Digest 8 - 14.02

Guide on Ruby concurrency, understanding Rails secrets\credentails, system tests in Rails with Minitest and other interesting things
14 February 2020   201

Greetings! I hope your week went great! Here's new Ruby news digest.

Learn about automatic image moderation with Amazon Rekognition, the easy way of configurating Kubernetes for Ruby, how to migrate from Rails API to Crystal and AWS Lambda and check more intesting stuff. 

Guides

  • Opening The Ruby Concurrency Toolbox

This guide covers threads, fibers, guilds with some practical comparisons

  • Automatic image moderation using Amazon Rekognition

Amazon Rekognition detects inappropriate content in images and it can be used in Ruby with ActiveStorage

  • Understanding Rails secrets/credentials

Basic guide about storing secrets and credentials that don't need to be stored in plaintext

  • Rubynetes: Kubernetes config the easy way

Learn how to use Ruby with Kubernetes without YAML

  • Getting Started With System Tests in Rails With Minitest

Beginners tutorial on testing in Rails using popular solution

  • My Experience Migrating a Rails API to Crystal and AWS Lambda – Part I

A story, which can be used as a tutorial for migrating from Rails API to Crystal and AWS Lambda

Articles

  • Rails introduces disallowed deprecations in ActiveSupport

A newspost with detailed code example on new ActiveSupport feature

Updates

  • GitHub CLI is now in beta

New GitHub command line tool is now available in beta 

  • The Twitter Ruby Gem

A Ruby interface for the Twitter API

  • httplog

This solution will help for networks working - allows to log outgoing HTTP request with Ruby