Rails 8 adoption is moving faster than the usual "everyone's stuck on old versions" narrative suggests. In early responses to the 2026 Rails Community Survey, Rails 8.1 is already the most-used version. The community is keeping up.
What version are you on? https://t.co/5Hgv77WSKA
Nothing like a headphone upgrade.
Got the HD 800 S a few months ago, paired with its ideal amp, the HDV 820. Yep, I could hear what makes them special, but I wasn’t blown away and didn’t enjoy the music as much.
Just got the Dan Clark Audio E3 and, man, now we are talking.
@yaroslav The S is supposed to be a bit more musical and have a bit more bass than the previous generation.
I am 100% into imaging, instrument separation, and detail retrieval. But, you can get all of that with a different sound profile.
Super cool news tonight: Rails realtime now runs on the server of your choice 🔥🔥🔥
Vova’s Action Cable server adapterization PR was merged 🥳. Same Channel and Connection code, swappable runtime underneath: Falcon, Fibers, async-cable.
This is the groundwork AnyCable has been proving in production for years, now landing in Rails itself.
People credit Rails’ longevity to DX. I think the secret behind it is adapterization pattern: every layer hides a default behind an interface, so the framework absorbs each new wave of innovation without a rewrite. Others wire it up with extra services. In Rails you swap the implementation as you wish, keeping the code intact.
Two years in the making, with
@ioquatix, @matthewd and @rafaelfranca steering the reviews. Congrats @palkan_tula 🥳
@josevalim In Elixir apps without types or guards, you don't idiomatically add type checks in test suites all over the place.
What these folks do not see is that it is OK for us that test suite errs. Ours is an optimistic approach, something will break.
Having done a bit of C, C++, Prolog, Common Lisp, Mathematica, Java, ..., the book that totally changed my career was Learning Perl, the llama book, in 2000.
I felt in love with dynamic languages, that was the power and the level of abstraction I wanted to work with.
@loicknuchel@Savlambda@Ciberon Well, this is not a thread about static vs dynamic.
It is a thread about common misconceptions about tests suites I see from (some) static typing folks.
@loicknuchel@Savlambda@Ciberon I have also seen statically typed code with embarassing exception trackers.
You need a test suite either way, and they do not differ that much, because you test business logic, not if such method returned an object of such type.
@loicknuchel@Savlambda@Ciberon In dynamic code bases runtime exceptions happen in the test suite, not in production.
What you are describing is non-idiomatic code and lack of test coverage.