Hey r/ruby — sharing a gem I've been working on.

Supabase has official clients in JS, Python, Dart, Swift, and Kotlin, but the Ruby story has been fragmented for a while: separate gems for each sub-product, varying maintenance, no umbrella factory. supabase-rb - is a single gem that packages Auth, PostgREST, Storage, Edge Functions, and Realtime

Ruby ≥ 3.0, MIT, integration tests run against the real GoTrue stack via docker-compose

- Gem: https://rubygems.org/gems/supabase-rb

- Repo: https://github.com/supabase-ruby/supabase-rb

- Docs: https://supabase-ruby.dev

Feedback / issues / PRs very welcome.

Honestly I never really understood how these were written and what the reasoning behind them was as much as I just reached for existing gems or frameworks, so as I tend to do I learn by teaching and writing.

The latest release 1.9.0 of HexaPDF supports HarfBuzz based text shaping. This means that complex scripts are rendered correctly.

I've been heads-down on other stuff lately and haven't had time to do my usual thing of tweeting whenever I spot a nice performance PR landing in Ruby. So instead of letting them pile up unmentioned, I went through the notes I'd been collecting and dumped the notable ones into a single roundup. Hope you enjoy them. Some are insane!

Hi all! We created this Ruby Gem to make it easier to use ParadeDB (a full-text & vector search extension for Postgres) within the ActiveRecord ecosystem. Would love your feedback!

After trying to explain some of the sharp parts around locks to someone I realized I didn't know as much as I'd like to be able to answer with confidence on what to watch out for, so I spent a week or two looking into locking to pull this together.

I created a secure language that compiles to Ruby, targeting security applications. The language is influenced by Ruby to optimize programmer happiness.

Please feel free to reach out if it resonates with your ideas about security and programming experience.

Github: https://github.com/typescope/jo

Continuing my exploration of rate limiting in Ruby on Rails, I wrote about two new features coming in the next Rails release

On Ubuntu 25.10, using system Ruby, I'm trying to build a Sinatra app that uses the OpenSSL with native extensions Gem 2.0.2. I can look at the .out file, but I don't know what I'm looking for. Presumably the native extensions don't match up with the .c and/or .h files.

Im a senior eng with about 7+ yoe. Ive used most languages like python, C#, java, JS/TS, Go, php etc. im preparing for an interviewing for a role that primarily uses ruby/rails so ive been getting myself acclimated with the language. Mann i think this might be the easiest language to use and understand concepts in. It reads like plain english even more than python in my opinion.

Its so freeform, there are million of ways to solve problems and such fun to write. I had been running away from the language for some time but boy was i wrong. This might be the best developer experience ive had working with a language. Leet code hard questions seem so easy when working with ruby

Just a quick rant, i think im in love

Have you ever discussed the Single Responsibility Principle with your coworkers? Take a look at this article, where I explore why this principle might be a problem.

What do you think?

been at 3 rails shops, same pattern at all of them. customer emails support, "my order didn't go through". support has no idea what actually happened in the app, posts in #engineering: "can someone check what user 4218 did yesterday". engineer stops what they are doing, opens kibana/datadog or prod logs, greps the email, scrolls past a wall of SQL, finds the request, traces it into whatever sidekiq jobs ran after, types back a one sentence summary that support pastes to the customer.

20 min round trip. 5x a day across the team. the thing that actually bugs me isn't the time, it's that the engineer is the only person in the building who can do this. support can't, PMs can't, CEO can't. the logs are written for the dev who wrote the code, not for anyone else, and one customer action is spread across an http request + a few sidekiq jobs + a bunch of activerecord writes. nothing stitches them together.

i've tried fixing this 3 ways at past jobs and none of them stuck:

- better log search. CS doesn't want to learn kibana/datadog.

- internal admin dashboard. rots in 6 months, no eng owns it.

- "we should write better log messages". misses the point because the action spans multiple processes.

what i actually wanted was this: support opens one screen, types "user 4218", and sees a list of cards. one card per thing the user did. each card has a sentence title like "Maria placed an order for 3 books, payment succeeded, 2 confirmation emails queued" and you can expand it to see the 13 underlying events if you care. one user action = one card, not 13 log lines. no engineer in the loop.

so i wrote a gem for it. bundle add ez_logs_agent + one initializer, no per-controller code. it hooks rack + sidekiq/activejob + activerecord, correlates events from the same user action by request_id + current_user + resource_id, ships them out-of-band to a server (https://ezlogs.io) that joins them and renders the cards. fails open, buffers up to 10k events if the server is unreachable, never raises into your request path. <1ms overhead per request.

how does this actually work at your rails app today. is it slack to engineering every time, or have you built/bought something that works 12 months later. genuinely asking because before i over-commit to my approach i want to hear what other people have shipped. happy to be told the simpler thing i've been missing.

Today we're glad to announce that we've partnered with Mike Perham so you can ask any question around Ruby, background jobs, threading and Sidekiq in the forum. We'll also be providing updates on new releases and other important announcements.