ggerman2025

I've been building ruby-libgd, a native Ruby binding to the GD graphics library.

This folder contains a Docker setup that runs JupyterLab with a full Ruby kernel — you can plot sin, cos, log, implicit curves like circles and ellipses, all in Ruby with no Python involved in the plotting.

The Plot class API ended up quite clean — plot.add("sin(x)") just works. Happy to answer questions about the implementation, especially the SafeMath evaluator and the implicit curve rendering.

Thanks for the clarification — that makes sense. My goal with ruby-libgd / libgd-gis is to provide a public, documented, reusable graphics and map-rendering stack for Ruby.

Not exactly.

That link looks like a Ruby-level drawing demo (and I don’t see a public repo or docs behind it).

ruby-libgd is a native, in-process binding to libgd, focused on deterministic rendering and explicit pixel-level primitives, released under the MIT license.

On top of that, I built libgd-gis (also MIT) as a higher-level standard: map rendering, GeoJSON ingestion, layers, tiles, and reproducible output for GIS-style workloads.

ruby-libgd is the low-level graphics engine; libgd-gis is the map renderer built on it.

Routing is the backbone of any Rails app, guiding every request to the right destination. But how confident are you that your routes won’t break during the next big refactor?

In my latest article, I dive deep into RSpec route testing—from the basics to advanced topics like nested routes, dynamic segments, and subdomain constraints. Whether you’re tackling a blog project or a complex multi-tenant app, this guide will help you:

Validate your routes with precision Catch regressions before they hit production Master best practices for efficient testing

Ready to level up your Rails game? Check out the full article and let’s discuss how robust routing can elevate your development process!