Can we please let humans write SOMETHING? There are AI-isms everywhere, which he even admits.
This reads like a Claude code comment; there is a ton of fluff, almost no content.
What was the "decision?" There are several entire paragraphs of purple prose setting it up, and I still can't answer it.
> This is not a post about assigning blame or pointing fingers. I’m as responsible for the state we’re in just as much as anyone else. The problem has been staring me in the face for so long I’m ashamed I didn’t realize the issue earlier.
> I know it hurts to hear that. I know full well that these are not the only issues facing the community. We have to start somewhere, and what I’m about to share with you is by far the biggest issue.
> The good news is that it’s a technical issue. And as you know, technical issues can be solved. But how in the world could a simple technical decision be responsible for such a huge downward trajectory? If you haven’t guessed it yet, this is a post about Rails. And I know that Rails doesn’t represent or speak for all of the Ruby community, but I want to highlight the numbers before I make my point.
Oh my god get to the point.
> I’m not going to go in depth into why Rails is the best framework for agentic coding, nearly two years of stories in the newsletter have covered that. I’m going to tell you why it’s the worst.
wtf
Ok, after rereading again, I found the "decision", which was to not merge ViewComponent. ¯\(ツ)/¯.
I'm telling my HS kids to NOT go into STEM, because over the next 10 years humans capable of writing like a human are going to be in huge demand.
Can we please let humans write SOMETHING? There are AI-isms everywhere, which he even admits.
This reads like a Claude code comment; there is a ton of fluff, almost no content.
What was the "decision?" There are several entire paragraphs of purple prose setting it up, and I still can't answer it.
> This is not a post about assigning blame or pointing fingers. I’m as responsible for the state we’re in just as much as anyone else. The problem has been staring me in the face for so long I’m ashamed I didn’t realize the issue earlier.
> I know it hurts to hear that. I know full well that these are not the only issues facing the community. We have to start somewhere, and what I’m about to share with you is by far the biggest issue.
> The good news is that it’s a technical issue. And as you know, technical issues can be solved. But how in the world could a simple technical decision be responsible for such a huge downward trajectory? If you haven’t guessed it yet, this is a post about Rails. And I know that Rails doesn’t represent or speak for all of the Ruby community, but I want to highlight the numbers before I make my point.
Oh my god get to the point.
> I’m not going to go in depth into why Rails is the best framework for agentic coding, nearly two years of stories in the newsletter have covered that. I’m going to tell you why it’s the worst.
wtf
Ok, after rereading again, I found the "decision", which was to not merge ViewComponent. ¯\(ツ)/¯.
I'm telling my HS kids to NOT go into STEM, because over the next 10 years humans capable of writing like a human are going to be in huge demand.
there are more issues currently than ViewComponent and I am planning to do video essay (not very technical one) on future of rails.
Overall, interesting read, although very heavy on bullet points
'Michael Carroll shared that “Matz is having the time of his life” working with AI.'
The downward spiral will continue because everyone apart from project leaders who apparently are too tired for development everyone hates AI.