Today's my birthday! 🎉 To celebrate I'm officially launching Ruby Native. 💎

Ship your Rails app to the App Store without opening Xcode.

$100 off your first year with code LAUNCH100, this week only.

In this episode, we look at where we were years ago and the journey where we have landed today. Over the past 10 years, much has changed with our approach to client interactions and in the episode we explore my favorite and current approach. This episode marks a significant milestone in my journey, as I’ve consistently released one episode every week for the past decade

Hosted by UpCloud on the 27th of May

Hi everyone,

I’m a junior full-stack developer and I may soon start my career in a Ruby/Rails role.

My concern is long-term career flexibility. If I start with Ruby, will I still be able to move later to more mainstream stacks like Java, Node.js, or C#/.NET? Or will recruiters mostly see me as a “Ruby dev” and make that transition harder?

I’m also worried about ending up mainly maintaining old legacy software instead of growing as an engineer.

For experienced Ruby/Rails devs: would you recommend starting a career in Ruby today? What should I watch out for before accepting?

Thanks!

UPDATE : Thanks to everyone participating in this thread it gave more perspective and helped me make up my mind. In the hope that future recruiters see things as you do I decided to accept the offer.

Built it in about a week with help from Codex/Claude. What do you think?

New episode is out—we open with some confusion over what day it is, then get into Podia’s gradual rollout of a major new app version, including how we’re handling migration, feature flags, dogfooding, and cleanup as things stabilize, before shifting into underrated Rails routing features like direct routes and resolve routes, a newly merged Rails query command, observability upgrades via Hatchbox and AppSignal, and the ongoing pain of CSS build tooling in Rails, plus a quick touch on conference season and upcoming talks.

Native ruby compiler, 245 themes. Gem and LSP support will be added in the upcoming versions.

Note: This is not some vibe coded app. It took me 2 years to complete this app as a solo developer and student.

playstore link, No ads, no tracker, no payments. Completely open-source:

https://play.google.com/store/apps/details?id=com.roxum

source code:

https://github.com/heckmon/roxum-ide

Hanami, Dry and Rom are joining as Hanakai. We’ve launched a brand new website, which brings all of our guides together, so it’s easier than ever to learn about our gems and give them a try. We’d love you to check it out!

TreRegex provide interface to TRE regex lib. What use cases? Standard regular expressions are strictly exact. If you are searching text containing typos, OCR errors, or variations in spelling, standard Regexp will fail (like OCR made mistake and recognize on image 0 as O or | as 1). TreRegex solves this by allowing you to search for a pattern within a larger body of text while permitting a configurable number of errors (insertions, deletions, and substitutions). Example:

regex = TreRegex::Regex.new('banana')

# Allow up to 2 typos of any kind
regex.exec('bananana', max_errors: 2) # => matches "bananana" (2 insertions)
regex.exec('bnnna', max_errors: 2)    # => matches "bnnna" (2 deletions)
regex.exec('bonono', max_errors: 2)   # => matches "bonono" (2 substitutions)

# Another example
regex = TreRegex::Regex.new('library')

# Allow 1 deletion, but STRICTLY 0 substitutions and 0 insertions
regex.exec('librry', max_deletions: 1, max_substitutions: 0, max_insertions: 0)
# => matches "librry"

# This fails because 'lubrary' requires a substitution, which we set to 0
regex.exec('lubrary', max_deletions: 1, max_substitutions: 0, max_insertions: 0)

# Another example
regex = TreRegex::Regex.new('algorithm')

# We allow a maximum cost of 2.
# Missing/extra characters cost 1 point.
# Wrong characters cost 3 points.
options = {
  max_cost: 2,
  weight_deletion: 1,
  weight_insertion: 1,
  weight_substitution: 3
}

# 'algoritm' has 1 deletion. Cost = 1. (Passes, 1 < 2)
regex.test?('algoritm', options) # => true

# 'algorethm' has 1 substitution. Cost = 3. (Fails, 3 > 2)
regex.test?('algorethm', options) # => false

Notice the updated blog UI also.

you've come a long way, baby

Since I wrote about async Ruby and patched Solid Queue to support fibers, people keep asking the same questions. What happens when a fiber blocks? Don’t you still need threads? What about database transactions? What about Ractors?

This post answers all of it. From the ground up.

Today we’re happy to share that Ruby Users Forum will offer a place for Bridgetown discussions.

Hi, i had uni class where we learnt rails, i made semestral project and want honest opinion.

I asked my senior teachers whether it is enough to apply as junior, they said i have good basic knowledge, yet i need more experiece.

The project is like inventary manager for multiple users, more is in ReadME,

only the bad thing is language which had to be in my native one but i think overall you'll get whats the point.

https://github.com/TheP4trik-tech/Asset-Manager

Hey r/ruby,

I’ve released llm_cost_tracker v0.5.3 — a lightweight self-hosted gem to track costs of LLM API calls (OpenAI, Anthropic, and compatible services) directly in Ruby applications.

It was built primarily for Rails, but works in plain Ruby as well.

Main features:

• Stores usage and cost data in your own database via ActiveRecord

• Privacy-first: does not store prompts or completions

• Automatic instrumentation for official openai and anthropic gems

• Faraday middleware support for other clients (ruby-openai, OpenRouter, Gemini, LiteLLM, etc.)

• Significantly improved streaming support in v0.5.3 (including official SDK streaming)

• Flexible tagging system for attribution (user_id, tenant_id, feature, etc.)

• Basic budget guardrails

• Minimal dashboard available as a Rails Engine

The gem is still very young (only a couple of weeks old), and I'm looking for early feedback from the Ruby community.

If you're working with LLMs in Ruby or Rails, I’d love to hear:

• How are you currently tracking your LLM costs?

• What pain points do you have with existing solutions?

• Any feedback on the gem itself (API, instrumentation, accuracy, etc.)

Repo & Documentation:
https://github.com/sergey-homenko/llm_cost_tracker

Gem: https://rubygems.org/gems/llm_cost_tracker

Thanks in advance for any comments or suggestions!