It looks like he spent about 4 minutes out of the 1:03 making that point.
replyI 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?
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.
replyI learned Ruby in 2007 people have been saying that about Rails every year since
replyI love Elixir/Erlang but we all know the "better stack" these new devs will choose instead for a web app is a maze of React, supabase, and Auth0.
It doesn't matter if Rails is well suited for AI or not. Now, there's less incentive and reasons to use it.
replyWhen 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
replySo 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?
reply