Live data from Hacker News

Returning to Rails in 2026

markround.com

11–20 of 254 posts

Re: Returning to Rails in 2026

#11
One thing that is not stressed enough, is Rails enforces good code patterns early on. If you follow the docs, you will know where model code should be, helpers should be, controllers should be. After all, it is an MVC framework.

However, modern day JS frameworks don't care about this at all. Most of them love flaunting about their raw performance numbers. Security? Fuck that. Not even basic form CSRF protection. A lot of times, there is not even SQL injection prevention in them.

Compound this with someone who just vibe codes their app on top of these frameworks - that's how you end up getting hacked. Every week there is an incident. That's why good frameworks like Rails are very important. People who actually care about writing secure, good quality software are on the decline, but thank God rails still exists as an option in 2026 despite the fact.

Re: Returning to Rails in 2026

#12
post #8

Earlier quoted context omitted.

> what's the difference if my agent uses fucking Next, Nuxt, Rails or Django? The claim seems quite clear to me: "convention over configuration allows coding agents to be more effective". But yes, I do agree that the main line should say what Ruby on Rails actually is, not why it's good for your agent.

There was a post last week about the best programming language for LLMs, and in the comments people loved Go, with the claim being it's very opinionated and there's really only one way of doing things. I'd say the same is mostly true for Rails apps as well. However having worked with Typescript for 8 years now... I'm not sure I could go back to Ruby without types. For LLMs thats important as well, the more guard rail…

Personally I love rust for agents because of types. In the ruby world there's sorbet and rbs so would be interesting to try that.

Re: Returning to Rails in 2026

#13
post #2

The main line on the Rails website now reads: > Accelerate your agents with convention over configuration. Ruby on Rails scales from PROMPT to IPO. Token-efficient code that's easy for agents to write and beautiful for humans to review And I fucking hate it. If I read this the first time I would think this is some kind of tool to optimize your LLM agents. I have been using Rails for over a decade now and always liked…

> what's the difference if my agent uses fucking Next, Nuxt, Rails or Django? The claim seems quite clear to me: "convention over configuration allows coding agents to be more effective". But yes, I do agree that the main line should say what Ruby on Rails actually is, not why it's good for your agent.

doesn’t forcing your agent to think in ruby put it at huge disadvantage though? since the language isn’t that popular it can’t have learned it as well as say python or Java?

Re: Returning to Rails in 2026

#14
post #11

One thing that is not stressed enough, is Rails enforces good code patterns early on. If you follow the docs, you will know where model code should be, helpers should be, controllers should be. After all, it is an MVC framework. However, modern day JS frameworks don't care about this at all. Most of them love flaunting about their raw performance numbers. Security? Fuck that. Not even basic form CSRF protection. A lo…

Javascript frameworks just do SSR + Express-style api routes. They don't handle SQL injection prevention because they don't deal with databases at all. CSRF prevention is less important in todays world tho.

Re: Returning to Rails in 2026

#15
post #2

The main line on the Rails website now reads: > Accelerate your agents with convention over configuration. Ruby on Rails scales from PROMPT to IPO. Token-efficient code that's easy for agents to write and beautiful for humans to review And I fucking hate it. If I read this the first time I would think this is some kind of tool to optimize your LLM agents. I have been using Rails for over a decade now and always liked…

I thought you were joking so I went to check it myself and... unfortunately you were not. That is insane.

Re: Returning to Rails in 2026

#16
post #2

The main line on the Rails website now reads: > Accelerate your agents with convention over configuration. Ruby on Rails scales from PROMPT to IPO. Token-efficient code that's easy for agents to write and beautiful for humans to review And I fucking hate it. If I read this the first time I would think this is some kind of tool to optimize your LLM agents. I have been using Rails for over a decade now and always liked…

Oh boy. I can't even imagine what sort of hell an AI could unleash on a language as dynamic and magical as Ruby...

Re: Returning to Rails in 2026

#17
post #2

The main line on the Rails website now reads: > Accelerate your agents with convention over configuration. Ruby on Rails scales from PROMPT to IPO. Token-efficient code that's easy for agents to write and beautiful for humans to review And I fucking hate it. If I read this the first time I would think this is some kind of tool to optimize your LLM agents. I have been using Rails for over a decade now and always liked…

> what's the difference if my agent uses fucking Next, Nuxt, Rails or Django? The claim seems quite clear to me: "convention over configuration allows coding agents to be more effective". But yes, I do agree that the main line should say what Ruby on Rails actually is, not why it's good for your agent.

>The claim seems quite clear to me: "convention over configuration allows coding agents to be more effective".

The agents pick up conventions from the extensive code in their corpus and aggressively follow them. I don't think Rails being explicit about it adds a lot unless someone is prone to prompting towards absurdity.

Re: Returning to Rails in 2026

#18
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…

I now also believe that at least Active Record is much easier to use than Django's ORM

Re: Returning to Rails in 2026

#19
post #2

The main line on the Rails website now reads: > Accelerate your agents with convention over configuration. Ruby on Rails scales from PROMPT to IPO. Token-efficient code that's easy for agents to write and beautiful for humans to review And I fucking hate it. If I read this the first time I would think this is some kind of tool to optimize your LLM agents. I have been using Rails for over a decade now and always liked…

Don't worry, it's just the hype phase and it will pass. (By 'pass' I mean agent-coding will be so ubiquitous that it's a given and not worth mentioning.)

Re: Returning to Rails in 2026

#20
post #18
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…

I now also believe that at least Active Record is much easier to use than Django's ORM

Doesn't matter when devs just slop out 400 lines of SQL and bypass the ORM.

Frameworks and structure will save you from neither stupidity nor ignorance.

Post reply on HN