Get a perfect quote

We’re eager to work with you. Please share your project goals and contact information. We respond to 97% of messages within 1-2 business day. Really!

TELL US ABOUT YOU

TELL US ABOUT YOUR PROJECT

What Are You Looking For?

Browse

Roobykon Ruby Digest: Issue 10

Back

roobykon_digest_10

Since we’ve decided our digest to come out monthly, a lot of awesome news have been kept on the back burner. But, nonetheless, we didn’t miss anything - the new Rails and Ruby update overviews, sharp guides, astonishing tutorials, and announcements - everything is here, in the latest Roobykon Ruby Issue! Let’s make sure you did not miss something worthwhile!

 

1. Rails 5.1.0.rc1: Loving JavaScript, System Tests, Encrypted Secrets, and more

 Ruby_on_Rails

Rails team have made a tremendous work again! With the help of the community, they’ve polished the Rails 5.1 release with more than 380 commits. Now, meet Rails 5.1.0.rc1 version with Action Cable; Action Mailer; Active Record; Active Support and more - all the changes are in the CHANGELOG, as always. Just follow the link to see the full list of changes.

 

2. Ruby 2.4.1 Released: What’s Changed

 Ruby_programming

Peter Cooper, creative editor, and programmer have made a great review of Ruby 2.4.1 main new features. All the changes compared to the previous version are in a rough order of priority, so it will be much easier to make a decision to follow the update (or not).

 

3. Understanding Ruby GC through GC.stat

 Ruby_code

Garbage collection in dynamic languages like Ruby is usually pretty complex, so Ruby developers prefer just to focus on writing code that really matters. But, suddenly, GC can become a problem - either it’s running too often or not enough, or the process is using tons of memory. Let's see how Ruby's GC works & what we can learn by reading some of the statistics.

 

4. Towards Minimal, Idiomatic, and Performant Ruby Code

 Ruby_webdevelopment

In this insightful article Thiago Silva, the senior software engineer from Brazil, tries to embrace a particular way of working with code: it should be minimal, idiomatic, and performant by default. If you are not already into this mindset, just dive into reading and consider getting into it.

 

5. Micro-optimizations matter: preventing 20 million system calls

 micro_optimizations

Micro-optimizations matter a lot, but the grade to which they matter is, of course, application specific. In this blog post, you will find a notable case where a micro-optimization (like removing a system call in a hot path) had a rough effect on software performance.

 

6. Want to use ES6 with Rails right now? Webpack to the rescue

 ES6_Rails

The next time you’ll feel the need to have classes & modules for better code organization - think about ES6! Here you’ll explore a great guide on how to configure a Rails app to write complex JS features with ECMAScript 6 code, and include it in applications without any effort.

 

7. Reading Ruby Code: ROM - Exploration

 Ruby_ROM

In this blog post, you’ll explore how the container method works and more generally the Container class. There's always a lot of things to be gained from code reading, on every skill level! The more seasoned developer will find here tons of interesting architectural patterns, and the beginners - get an idea about the usage of nested fetch to achieve auto-loading.

 

8. Five Features You Can Use in ES6 Today

 ES6_features

The changes in ES6 have been massive, exciting, and confusing. In this essay, the experienced developer at PubNub Joshua Marinacci introduces five features of the new JavaScript that you can use right away to supercharge your code and points what features to hold off on.

 

9. Embracing Change: Rails 5.1 Adopts Yarn, Webpack, and the JS Ecosystem

 Yarn_Webpack_JS

Let’s see how Rails has begun integrating Yarn and Webpack and along the way, dive into these new technologies to get a better understanding of how they work. JavaScript developers will definitely be jealous with how easy it is to use their own toolsets.

 

10. Why you Should not use a Class as a Namespace in Rails Applications

 Rails_Bug

In case you are using a class as a namespace - it can produce a bug that doesn’t always show up on the surface. Be sure that you have different names for your model class and your namespace in Rails apps. All the details are under the link!

 

Rate Roobykon Software