Book Image

Polished Ruby Programming

By : Jeremy Evans
Book Image

Polished Ruby Programming

By: Jeremy Evans

Overview of this book

Anyone striving to become an expert Ruby programmer needs to be able to write maintainable applications. Polished Ruby Programming will help you get better at designing scalable and robust Ruby programs, so that no matter how big the codebase grows, maintaining it will be a breeze. This book takes you on a journey through implementation approaches for many common programming situations, the trade-offs inherent in each approach, and why you may choose to use different approaches in different situations. You'll start by refreshing Ruby fundamentals, such as correctly using core classes, class and method design, variable usage, error handling, and code formatting. Then you'll move on to higher-level programming principles, such as library design, use of metaprogramming and domain-specific languages, and refactoring. Finally, you'll learn principles specific to web application development, such as how to choose a database and web framework, and how to use advanced security features. By the end of this Ruby programming book, you’ll be a well rounded web developer with a deep understanding of Ruby. While most code examples and principles discussed in the book apply to all Ruby versions, some examples and principles are specific to Ruby 3.0, the latest release at the time of publication.
Table of Contents (23 chapters)
Section 1: Fundamental Ruby Programming Principles
Section 2: Ruby Library Programming Principles
Section 3: Ruby Web Programming Principles

Designing plugin systems

Having a defined plugin system for a library can be a huge advantage. Libraries that do not have a plugin system usually handle extensions to the library in an ad hoc manner that differs per extension. With a plugin system, extensions to the library operate in a uniform manner for each extension. This has the following advantages for everyone involved:

  • The library creator can create the plugin system that works best for their library, allowing extensibility in the parts that should be extensible, and not allowing extensibility in parts that do not need to be extensible.
  • The plugin creator can review the plugin system to determine how the library should be extended, such as which extension points exist. They probably also have many other examples of extensions to the library that they can review, which makes the process of building their plugin much easier.
  • The library user knows how to use the plugin system for all of the library's extensions...