Remix.run Logo
▲ dmix a day ago

> If you watch the talk, he is not anti-rails.

He explicitly said he still loves ruby as a language and thinks Rails is well suited for a future with AI coding.

It's interesting how this stuff gets spun on social media by people who don't watch the content.

▲Lio a day ago | parent | next [-]

It looks like he spent about 4 minutes out of the 1:03 making that point.

I can't but help think that he would have spent longer on it if that's what he really thought.

I don't think he believes in Rails any more.

It's clear that he was more excited about thing that are not ruby or rails and now considers rust better suited to the output of AI.

To be honest, I could see rust taking over from typescript/javascript as an output language for the web too. If no one needs to read source code any more why not use rust for everything?

▲treis a day ago | parent [-]

I don't think anyone should really believe in Rails at this point. It was a monumental leap forward at the time but other stacks have shown that there are better ways.

▲ a day ago | parent [-]
[deleted]
▲ksec 19 hours ago | parent | prev | next [-]

>It's interesting how this stuff gets spun on social media by people who don't watch the content.

I watched it live, and a few actually in the show have very different perspective to what you suggest, they were just keep it to themselves and not posting it on twitter. Some did, but then deleted it.

And no one is questioning he doesn't like ruby anymore. But it was obvious there was nothing much said about the future of Ruby and Rails.

▲Scarbutt a day ago | parent | prev [-]

It doesn't matter if Rails is well suited for AI or not. Now, there's less incentive and reasons to use it.

▲lackoftactics a day ago | parent [-]

When I started as rails dev in 2013, it was really the top solution for producing MVP fast. Now, I don’t think that’s the case and most of the incentives are gone if we are no longer writing code by hand

▲james_marks a day ago | parent | next [-]

I prefer a Rails backend, especially in the agentic world.

With an agent on a greenfield is when I’m most reliant on a framework for good standards and a clear architecture.

This is one of the things Rails does really well.

▲mattbrewsbytes a day ago | parent | prev | next [-]

So what would you pick for producing an MVP web app fast that you also want to run in production, maintain, patch and scale that has a solid eco-system of pre-built libraries you can just plug in to solve problems?

▲timr 12 hours ago | parent | prev [-]

I strongly prefer Rails with agentic development. Rails comes with nearly everything you need to make a full-featured application, and that makes it easier and faster to use with agents.

No other framework comes close, and telling me that I can have my agents cobble together this same baseline, badly, from a hodgepodge of new code and random libraries is not compelling.