Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Returning to Rails in 2026

markround.com

Post reply on HN
Print view View original

141–150 of 254 posts

Re: Returning to Rails in 2026

#141

Post by paozac »

Zanfa wrote: post #38
paozac wrote: post #10

I love rails and the recent improvements are great. I have the impression, though, that these days it only appeals to those who picked it up before version 3 or 4, when it was smaller, maybe more understandable, and incredibly better than all the competing frameworks (except Django maybe). If your first contact with rails is version 7+ and you’re only comfortable with JS/TS, then you’re not going to get it and might…

> If your first contact with rails is version 7+ and you’re only comfortable with JS/TS, then you’re not going to get it and might actually strongly dislike it This is the primary issue with Rails in my experience. It takes intentional effort to internalize the idioms before it clicks and you unlock the magic that makes it so insanely productive. JS devs will keep trying to force backend business logic into Franken-R…

Yes, I've seen that, too. The rails way of doing things can feel like a terrible limitation to some developers, while others enthusiastically embrace it

Re: Returning to Rails in 2026

#142

Post by the__alchemist »

f311a wrote: post #37

I love the batteries that RoR or Django gives you, but then I also remember how much time it takes to maintain old projects. Updating a project that was started 5-6 years ago takes a lot of time. Part of that is managing dependencies. For Django, they can easily go above 100. Some of them have to be compiled with specific versions of system libraries. Even Docker does not save you from a lot of problems. Right now, I…

Different experience with Django. I am only using a handful of deps. dj-database-url, dj-static, gunicorn, psycopg are the only "mandatory" or conserved one IMO as a baseline.

Re: Returning to Rails in 2026

#144

Post by evolve2k »

konart wrote: post #134
h4ch1 wrote: post #121

Earlier quoted context omitted.

Are we that far gone that "hand coding" is a term now? I hope there's an /s missing

I hope "hand coding" is an antonym for "convention coding" or something.

I’m guessing hand coding means, not vibe coding.

Did you use AI? .. Nah I hand coded it.

Re: Returning to Rails in 2026

#145

Post by vidarh »

draw_down wrote: post #116
sensanaty wrote: post #110

I love Rails, but after working for a few places with huge Rails codebases and then several other places with .NET and other frameworks with actual typing, I just can't go back to Rails for anything that isn't a personal project. Working with a large codebase with an untyped codebase is just a nightmare, even with powerful IDEs like RubyMine that are able to cover some of the paint points. I wonder how good Sorbet is…

I’ve worked in two places now with Ruby Sorbet servers. Ruby always drives me nuts how things are just in-scope and we don’t know why or where they came from. I certainly wouldn’t want to go back to working in dynamic languages without typing on top. That takes too much brain power, I’m too old for that now. I would say Sorbet seems more “basic” than something like Typescript. It handles function calls matching signa…

> Ruby always drives me nuts how things are just in-scope and we don’t know why or where they came from.

irb(main):005:0> Foo.new.method(:bar).source_location => ["tmp/test.rb", 5]

Re: Returning to Rails in 2026

#146

Post by Cyphase »

evolve2k wrote: post #144
konart wrote: post #134

Earlier quoted context omitted.

I hope "hand coding" is an antonym for "convention coding" or something.

I’m guessing hand coding means, not vibe coding. Did you use AI? .. Nah I hand coded it.

Real programmers use butterflies. https://xkcd.com/378/

Re: Returning to Rails in 2026

#147

Post by vidarh »

satvikpendem wrote: post #127
kshahkshah wrote: post #115

Earlier quoted context omitted.

Are you hand coding?

Doesn't matter because LLMs also benefit greatly from typed code bases in that they can run the type checker and fix the problems themselves on a loop.

Both Claude and Codex handle Ruby just fine.
Post reply on HN