4 ms·

Alright, somebody has to draw the line somewhere. Every time DHH goes off on one of his little rants and angers a lot of people in the process it's not just th

Alright, somebody has to draw the line somewhere. Every time DHH goes off on one of his little rants and angers a lot of people in the process it's not just those people that get affected, and not just emotionally either. These Ruby [on Rails] dramas have a real-world impact on the rest of us, the hundreds of thousands of us that use Rails every day to make a living. It affects us in that it makes us all look like unprofessional schoolground children. Rails already has a stigma of "hipster" developers that tend to be up their own asses, and episodes like this really don't help our image. Especially not when the global developer community is not as massive as you'd like to believe, especially when people talk - to other developers, to potential and existing clients that then get per-conceptions of unprofessionalism, and to newbie developers that shy away and look into alternative languages and frameworks because they don't want to be associated with this wankery. DHH's post, particularly the second paragraph, seriously comes across as if the core "team of chefs" is doing us all a massive favour and if we want to keep benefiting from the really beautiful thing that Rails is then we should shut the fuck up and take what we're given. Well this isn't Pyongyang (if we're going to play with metaphors) and DHH is not our dear leader. Yes of course I, and all the other Rails developers and immensely grateful for the framework's existence, but it's OSS now. There are thousands of contributors and so many more times commits than that to the projects since it did become OSS. The community either needs a revolution or a fork because this downward spiral of foul air is just going to continue spreading and affecting us all. I'm sure if a couple of well respected individuals decided to take that route, a whole lot of people would back them up - I know I sure as hell would. Pawel - a Rails developer.

pretoriusB 14y ago
>Pawel - a Rails developer. I'd like people adding those kinds of claims to also give an estimate of how much they have contributed to the project. I.e. John S., Linux Kernel developer, contributed maybe 10 lines of code, or 0.0001% of the kernel source or: L. Torvalds, Linux Kernel developer, wrote the kernel code from scratch, that's my name on the project, biatches Else, this "a Rails developers" signature tells us we should give extra credit to your opinion, but we don't know how much compared to DHH. I don't mean it about you, Pawel, or your comment (I don't follow Rails that much anyway the last 2-3 years), I mean it in general.
- rachelbythebay 14y ago
  Are you sure they're all claiming the same thing? Maybe one "Rails developer" actually works on the framework itself, while another "Rails developer" is a developer who merely uses it to accomplish something else. Either way, you're looking at a brag-fest as people try to one-up each other. That can't be productive. I don't think any good would come of this.

pretoriusB 14y ago

>Pawel - a Rails developer. I'd like people adding those kinds of claims to also give an estimate of how much they have contributed to the project. I.e. John S., Linux Kernel developer, contributed maybe 10 lines of code, or 0.0001% of the kernel source or: L. Torvalds, Linux Kernel developer, wrote the kernel code from scratch, that's my name on the project, biatches Else, this "a Rails developers" signature tells us we should give extra credit to your opinion, but we don't know how much compared to DHH. I don't mean it about you, Pawel, or your comment (I don't follow Rails that much anyway the last 2-3 years), I mean it in general.

rachelbythebay 14y ago
Are you sure they're all claiming the same thing? Maybe one "Rails developer" actually works on the framework itself, while another "Rails developer" is a developer who merely uses it to accomplish something else. Either way, you're looking at a brag-fest as people try to one-up each other. That can't be productive. I don't think any good would come of this.