# ruby programming language Published articles for ruby programming language. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Chainguard Releases Ruby 4.0 Packages and Container Images DevFeed: [Chainguard Releases Ruby 4.0 Packages and Container Images]() Original publisher: [Read original article]() Published: 2025-12-26T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [Ruby](), [chainguard](), [chainguard containers](), [Containers]() Tags: [architectures](), [chainguard](), [chainguard-containers](), [chainguard-ruby-image](), [cmvp](), [container-images](), [containers](), [fedramp](), [ruby](), [ruby-programming-language]() ### AI overview Chainguard announces packages and container images for Ruby 4.0, which includes performance improvements and language refinements. The images support x86_64 and ARM64, include stated hardening and runtime-security features, and are available through Chainguard, Docker Hub, and AWS Public ECR. ### Source excerpt Chainguard delivers Ruby 4.0 container images: secure, zero-CVE, FIPS-ready, and available free so developers can adopt the latest Ruby safely and fast. ## The Case Against Monkey Patching, From a Rails Core Team Member DevFeed: [The Case Against Monkey Patching, From a Rails Core Team Member]() Original publisher: [Read original article]() Author: Eileen Uchitelle Published: 2023-02-21T14:00:04Z Content type: opinion Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Rails](), [Ruby](), [Programming](), [Open Source]() Tags: [framework](), [open-source](), [pull-request](), [ruby](), [ruby-programming-language](), [shopify]() ### AI overview This opinion argues that Ruby monkey patches should be used sparingly, if at all, because they are brittle, dangerous, and often unnecessary. It defines monkey patches as dynamic changes to existing code, discusses an Active Record adapter that altered MySQL query-warning behavior, and describes upstreaming that behavior into Rails to remove the patch. ### Source excerpt Monkey patching is considered one of the more powerful features of the Ruby programming language. However, by the end of this post I'm hoping to convince you that they should be used sparingly, if at all, because they are brittle, dangerous, and often unnecessary. I'll also share tips on how to use them as safely as possible in the rare cases where you do need to monkey patch. ## Using GraphQL with Ruby on Rails DevFeed: [Using GraphQL with Ruby on Rails]() Original publisher: [Read original article]() Author: Erin Fox Published: 2021-11-18T11:00:05Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [Ruby on Rails](), [Ruby](), [mvc](), [API](), [Framework](), [web applications](), [Programming language](), [Front end](), [React]() Tags: [api](), [apis](), [apollo](), [applications](), [architecture](), [backend](), [business-logic](), [community](), [declarative](), [framework](), [frontend](), [graphql](), [how-to](), [mvc](), [programming](), [rails](), [react](), [ruby](), [ruby-on-rails](), [ruby-programming-language](), [web-applications]() ### AI overview A tutorial introducing Ruby on Rails and GraphQL, then demonstrating how to build and query a Rails-GraphQL API with React and Apollo. ### Source excerpt Objective: Learn how to create a new project with Ruby on Rails and GraphQL while setting it up to use React and Apollo. The focus is on getting the API running and executing a query. Introduction Ruby on Rails is an MVC (model, view, controller) framework that you can use to build web applications using the Ruby programming language. GraphQL is a declarative query language and server-side runtime that makes it easier for frontend developers to perform data fetching. ## Ruby Private Class Methods DevFeed: [Ruby Private Class Methods]() Original publisher: [Read original article]() Published: 2016-01-24T12:00:00Z Content type: tutorial Language: en Sources: [Jake Yesbeck]() Topics: [Ruby](), [Programming](), [Code](), [Programming language]() Tags: [code](), [programming](), [programming-language](), [ruby](), [ruby-programming-language](), [syntax]() ### AI overview This tutorial explains Ruby method visibility, focusing on how to define private class methods. It contrasts instance methods, class methods, public, private, and protected visibility, then shows why a direct private declaration can fail for a class method and introduces eigenclass syntax as an alternative. ### Source excerpt In the Ruby programming language, defined methods come in two variants: instance methods and class methods. Instance methods are available after an object has been initialized, creating an instance. Class methods, on the other hand, are available without creating an instance of the class they are defined upon. Ruby methods can vary in visibility. Public methods are available in any context, while private methods' availability is restricted within the instance of a class and its descendants. A third visibility scope, protected, behaves similarly to private methods, but protected methods can be called by other instances of the same class. For a quick refresher, public and private instance methods look like this: class Dog def do_trick bark end private def bark puts 'woof woof' end end When the public method is called: > dog = Dog.new > dog.do_trick # => woof woof And the private method: > dog = Dog.new > dog.bark # => NoMethodError: private method `bark' called for Private class methods might not be as common as private instance methods, but they still have their place. For instance, a class method may require internal helper methods to complete its function. Whatever the reason, defining private class methods has value but is not always intuitive. This example Dog class needs to maintain a list of tricks that will be used within the other public class methods. This list should not be accessible to any callers outside the Dog class. The wrong way A first pass at writing the private tricks method could look like: class Dog private def self.tricks [:bark, :roll_over, :fetch] end end However, when testing the visibility of the tricks method: > Dog.tricks # => [:bark, :roll_over, :fetch] Uh oh, no error was thrown indicating a that a private method was called, this method is completely public. Why? The reason that the above code did not produce a private method has to do with Ruby's object hierarchy, interactions amongst internal classes, instances of those classes, ## Learning Ruby DevFeed: [Learning Ruby]() Original publisher: [Read original article]() Published: 2011-10-28T00:00:00Z Content type: opinion Language: en Sources: [Radek Pazdera]() Topics: [ruby programming language](), [Programming](), [Learning]() Tags: [book](), [installation](), [learning](), [programming-language](), [ruby](), [ruby-programming-language](), [tutorials]() ### AI overview A personal introduction to learning Ruby that reviews online and print resources for beginners, discusses Ruby installation on Linux and Windows, and briefly presents a first Ruby example. ### Source excerpt My personal take on learning the Ruby programming language