Ways to evaluate a gem

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

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.

NGINX to Release Unit 1.3 Beta

Developers expanded the ability to run web applications in Python, PHP, Perl, Ruby and Go
16 July 2018   60

In open access, a beta version of the NGINX Unit 1.3 application server was released. Developers continued to expand the ability to run web applications in Python, PHP, Perl, Ruby and Go. The project code is written in C and is distributed under the Apache 2.0 license.

Features

Version 1.3 eliminates the problems with handling errors when installing HTTP connections.

Among other changes:

  • parameter max_body_size to limit the size of the body of the request;
  • new parameters for setting timeouts when setting up an HTTP connection:
         "settings": {
              "http": {
                  "header_read_timeout": 30,
                  "body_read_timeout": 30,
                  "send_timeout": 30,
                  "idle_timeout": 180,
                  "max_body_size": 8388608
              }
          },
  • automatic use of the Bundler where possible in the Ruby module;
  • http.Flusher interface in the module for the Go language;
  • The possibility of using characters in the UTF-8 encoding in the request headers.

The first version of the NGINX 1.1 application server was released in mid-April 2018. Under the control of NGINX Unit, several applications can be executed simultaneously in different programming languages, the startup parameters of which can be changed dynamically without the need to edit the configuration files and restart.