Ruby on Rails is Dead (2026 Edition)(mroczek.dev)

3 pointsby lackoftactics2 ay önce3 comments

Ruby on Rails is Dead (2026 Edition)

https://mroczek.dev/articles/rails-dead-2026/

3 comments

earcar2 ay önce

If there's anything that our community doesn't need is exactly these posts. We have excellent gems, the only thing we lack is good marketing, and better documentation of certain pieces. Posts like this perpetrate the same culture that we want gone.

To the points the post makes: as the author of RubyLLM, I've built several chat interfaces streaming from LLMs with Hotwire. They handle token by token streaming, full message restreaming at the end, role parsing, etc. They work great and the code is concise and beautiful.

Certain apps' hot paths are on the client, so it makes sense that Figma pays a lot of attention to that. However, did you know that Figma use Rails under the hood?

Ruby deserves a different story than what's shown here.

lackoftactics2 ay önce

According to this thread on LinkedIn and comment by Pragmatic Engineer Gergely Orosz.

https://www.linkedin.com/posts/gergelyorosz_figma-is-going-p...

Figma stack is: > plain Ruby, plus Sinatra and ActiveRecord

Full article about their stack. It’s not rails. https://open.substack.com/pub/pragmaticengineer/p/inside-fig...

pmontra2 ay önce

I'm making more than 50% of my money from a Rails app providing a JSON API to a Vue frontend. The only HTML sent by Rails to the browser is a page with the Vue code and the initial data.

It's not the first web app with a similar architecture I worked on in the last 10 years. The only traditional app I've been working on recently is a Django app that generates HTML pages, with some JS. AI is helping not to turn that JS into a mess.