On 29/07/2009, at 12:05 PM, Glen Maddern wrote: > But, I also think that if 'using Ruby' is the only differentiating > feature about your web development company then you're in other > sorts of trouble. To me, that's starting down the closed-source road > - I don't want my competitor to have the same tools I've got/helped > develop. The goal should be to be winning jobs and satisfying > customers with the quality of your work, regardless of the tools you > or your competitors use. > > But then, I'm not currently running a web dev shop so I understand > the commercial reality might preclude a lot of people from chasing > this goal.
I know I'm being noisy, so I'm going to pipe down now. But Glen, on this point: one shouldn't be ashamed right now to see using Ruby -- and Rails, and related technologies -- as a competitive advantage. Because of what they let you do, and do quickly and well. Personally I would be deeply ashamed (and quickly out of business) if it were our only selling point. I'd also be ashamed if I took without giving back. It is definitely about quality, about what you do to ensure it and promote it. > One final point, in my experience, the people making Ruby or > anything else that's 'cool' available to the Enterprise generally > work in/for one. Like any embarrassing topic, the long-suffering, > overpaid and unchallenged friend is actually themselves. It's why I > hack on Scala in the evenings and scheme up ways to get it used in > the Java shop where I work. Point well made. - J PS: Lachlan nailed it too. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
