3 ms·
Nice post, Matt. I think that you're absolutely right. It doesn't do well for the mind share of the framework if it requires a CS degree to deploy. But then,
by iamelgringo 19y ago
Nice post, Matt. I think that you're absolutely right. It doesn't do well for the mind share of the framework if it requires a CS degree to deploy.
But then, DHH has never really said that he was passionate about the users of his framework. For an example, see the image below.
http://pocoo.org/~mitsuhiko/rails_motivation.jpg http://pocoo.org/~mitsuhiko/rails_motivation.jpg
DHH has long said that he improves Rails based on what he and 37 Signals needs, and not what the community needs. His attitude seems to be that it's his framework and he can do what he wants to.
So, no. I don't really see the Rails hosting issue being fixed any time soon.
- mechanical_fish 19y agoHis attitude seems to be that it's his framework and he can do what he wants to. No. His attitude is that it is your framework, so get to work! People seem to think that Rails would run just fine on their $5.99 web hosts if the core team would deign to assert its magical force of will. Well, as my old boss used to say: "them" is "us". If you know how to make Rails run, profitably and reliably, on a cheap-ass shared host, go start the business and enjoy your profits. If you don't know, stop assuming that it's because DHH and Ezra Z. are holding out on you. They don't know, either. Rails is all of four years old, and (unlike PHP) was not designed with the explicit goal of supporting shared hosting. I like Rails, and am glad you like it too, but stop expecting miracles.
- mattmaroon 19y agoI don't think anyone is expecting miracles, or for DHH to make it his personal goal to adapt Rails for the shared hosting environment. The original blog was simply pointing out that if Rails wants to see the kind of widespread adoption PHP has, that's what the community is going to have to do. It's correct. People keep misinterpreting or misunderstanding the argument.