Absolutely yes, all over the place! Startups are building greenfield software with Rails as we speak. Loads of established businesses have Ruby applications that are quietly chugging along doing their jobs well. & Shopify, a company with $1.6 billion in annual revenue, uses Ruby _very_ heavily & also invests in the wider Ruby ecosystem.<p>Ruby is not without its drawbacks & drama, but it’s elegant in a way that few languages are to this day (how many JS programmers _actually_ grok prototype-based object-orientation?) & compared to NPM, RubyGems is (lately) unexciting in the best way.
For pretty much everything. My terminal is in Ruby, with a Ruby font renderer, running Ruby shell, and my editor is in Ruby, my window manager, my file manager.<p>(Yes, I'm taking it a bit far; my prototype Ruby compiler is self-hosting finally, so I guess sometime in the next 20 years I'll end up booting into a Ruby kernel for no good reason...)
I really like Ruby. It had a formative impact on my young programmer self, particularly the culture. So much joyful whimsy.<p>But like... something like a font renderer in Ruby? The thing that is incredibly cache sensitive and gets run millions of times per day on a single machine? The by far slowest step of rendering any non-monospaced UI?<p>The Earth is weeping my brother.
It <i>doesn't</i> typically get run millions of times per day because in most regular uses it's trivial to cache the glyphs. I use it for my terminal, and it's not in the hot path at all for rendering, as its only run the first time any glyph is rendered at a new size. If you want to add hinting and ligatures etc., it complicates the caching, but I have no interest in that for my use, and then it turns out rendering TrueType fonts is really easy:<p><a href="https://github.com/vidarh/skrift" rel="nofollow">https://github.com/vidarh/skrift</a><p>(Note that this is a port of the C-based renderer libschrift; the Ruby version is smaller, but much less so than "usual" when converting C code - libscrift itself is very compact)
Ruby is amazing. The software industry has suffered because people think Ruby isn’t the right choice and try to static type all things.
People should. I seriously miss using it at my day job. It's not for code where type systems make things a lot more stable, but it's great for scripting and quick things. Also ORMs in ruby are truly nice, and I haven't found anything as good anywhere else.<p>Generally speaking Ruby has the best APIs.
I actually think types are an anti pattern. I’ve seen more code with type escape hatches than bugs in Ruby. The truth is if you follow TDD and good coding patterns the bugs in a dynamic environment are unlikely to show up.
Frameworks and packages, sure. I’m not sure I would agree with APIs.<p>ActiveAdmin is best in class, Rails is fantastic; but there’s a lot of insanity in the API for a language that “gets out of the way” and “just works”<p>Slice is my favorite example. (It’s been a bit since I’ve used it)<p><pre><code> [0].slice(0, 100) == [0]
[].slice(0, 100) == … </code></pre>
exception? Or nil? Why does it equal []?<p>For a “give me an array back that starts from a given, arbitrary index, and auto-handle truncation” not having that behavior continues to confuse me from an intuitive perspective. Yes, I understand the source of it, but why?
Because [] is an array with nothing in it, and [0] is an array with something in it.<p>So saying “give me the array containing the first 100 elements of this array with one element” would obviously give you the array with one element back.<p>Saying “give me the array containing the first 100 elements of this array with zero elements” would follow that it just gives the empty array back.<p>On top of that, because ruby is historically duck-typed, having something always return an array or an error makes sense, why return nil when there’s a logical explanation for defined behavior? Ditto for throwing an error.<p>Seems thoughtfully intuitive to me.
because it's meant to be a more functional language. if slicing an array out of bounds threw an error it would be java.<p>[].slice(0, 100).each do |x|
puts x
end<p>that shouldn't be an error and it seems to be the principle of least surprise imo.
Ruby on Rails is the GOAT. Nothing comes close in joy and productivity, even in 2026.
What’s the right way to take this?
It's my daily language and I don't even use rails nowadays.
I use Rails for many of my side projects. Because of the emphasis on convention over configuration, Rails codebases tend to be succinct with minimal boilerplate, which keeps context windows small. That in turn makes it great for agent-assisted work.<p>For web stuff, with server-side rendering and partials it means minimal requirement to touch the hot mess that is JavaScript, and you can build PWAs that feel native pretty easily with Hotwire.<p>Ruby is slow as fuck though, so there's a tradeoff there.
ruby and rails is the only stuff that keep me doing web development.<p>when I touch js, and python... I prefer ONLY AI agentic style of working.