News for hackers. Stuff that matters.
Re:Returning to Rails in 2026 by eudamoniac on Thursday March 12, 2026 @11:30AM (#47352204)
I worked with Rails a lot. In my experience, every rails dev who is fanatical about how much they love Rails, also has little to no experience with strong types. Of the ones who later try types, they no longer love Rails. Personally I quit Rails entirely because of lack of types. No, RBS and Sorbet are not even close to good enough.

Also, every enterprise rails app I've seen (seven, to date) has been really poorly written/architected in a way that other backends just weren't. Even the fairly new ones felt like legacy code already.

Re:Returning to Rails in 2026 by mike_ivanov on Thursday March 12, 2026 @02:23PM (#47355091)
Ruby is a strongly typed language. I think you are confusing strong typing with static typing.
Re:Returning to Rails in 2026 by goatlover on Thursday March 12, 2026 @05:29PM (#47357390)
And by contrast, C is static but weakly typed.
Re:Returning to Rails in 2026 by schlch on Thursday March 12, 2026 @04:49PM (#47356887)
I still really like rails. It’s really fun until your codebase reaches a certain size. At that point you better have a large suite of test which becomes a problem of it self because the tests will take forever to complete.

I tried sorbet a couple of times and totally get why it’s useful but imo it’s not just lacking (e.g. compared with what can be done with TS or even a simple type system like golang) but it also removes all the fun parts of ruby / rails.

Re:Returning to Rails in 2026 by eudamoniac on Friday March 13, 2026 @03:08PM (#47368341)
Right, the test culture is very silly to me. Thousands of tests and long CI times, basically just doing a poor invention of a compiler. Dynamic types are so much extra work.