More reasons for Rails NOT to be mainstream 11
Kevin Clark, a fellow #cabooser, and great programmer posted an article on his blog today that for one reason or another sparked some contraversy. He wrote about Rails coding practices that he believes (either through experience or following the core mailing list) should not be used anymore. The pros and cons of scaffolding in production, engines, components, protected instance variables and help vampires are all things that have been discussed openly in various venues and Kevin advocated against them with his reasons why.
What happened next is hard to describe but it's like a pack of wolves came out and shredded him apart. Not sure where these "Rails" programmers came from but I hope they don't stick around. Besides, how can you get upset at a guy that looks like a cute little chia pet?

What happened next is hard to describe but it's like a pack of wolves came out and shredded him apart. Not sure where these "Rails" programmers came from but I hope they don't stick around. Besides, how can you get upset at a guy that looks like a cute little chia pet?
I think the reaction to the reaction to his post is overblown. Most of the points were good, but when other points aren't backed up with alternatives and evidence and specifics, then seasoned Rails programmers do get a bit riled up, especially when their own experience runs counter to his claims and when it's the first time that a coding practice has been claimed as "something you shouldn't be doing." Like pagination -- never before has it been claimed as "bad" or "deprecated" that I've seen.
I think many people don't know that Kev looks like a cute Chia pet because they just don't know Kev. They took umbrage about being told what they're (about to be) doing wrong, rather than felt ralllied and called to action and inspired to change. It's a tone thing.
I know Kevin, and I've already seen some of those warnings in edge, so I skimmed through his article like any other and smiled at his tongue-in-cheek moments. But I understand where many others might have come to different conclusions.
What backlash I see is only normal when telling a passionate, vocal community who fundamentally cares about doing things right that they are, in fact, doing things wrong, with more sarcasm than solution.
To some it was a funny and helpful list, to others it has an uncomfortably caustic sting with an edge of truth to it and the weight of a considerable amount of authority in the community.
...that being said, we live and we learn, right? I learned a couple things that I should change in a project of mine, and I think Kevin's learning plenty about the differences between facetious and sarcastic! :)
I also agree that Alex's response was out of proportion to the situation. Alex says in a comment that his intention wasn't to personally attack Kevin, but it really doesn't help that the post names him five times in nearly as many paragraphs, with a number of colorful metaphors and adjectives thrown in for good measure...