I think you've either not read the article completely, or failed to understand the central point that the author tried to illustrate. The issue is with culture

I think you've either not read the article completely, or failed to understand the central point that the author tried to illustrate. The issue is with culture. There is no problem if rails wants to go one way, and the author wants to go another. The issue at hand is that Rails is stymieing growth, not just in its own ecosystem but in the ruby ecosystem as a whole. I think this is a very good point, and in contract I can imagine that if Django had total and utter dominance in the python world, python would be in a similar position.