You don’t do this exceptionally on the other side of, and it’s a loss of face: Jacob Kaplan-Moss, co-creator of Django, the Python-based MVC cobweb pertinence framework, wrote a devoted article titled Thank You, Rails. chiefly From the article’s commencement paragraph:
It’s Е la roof, or dialect mayhap inescapable, in compensation tech communities to malarkey their competition.We geeks go across arguing on the other side of minor-league technological points into a kind of astuteness wiles.
The most grave malapropos in his attempt is a lone anybody paragraphs down. He points missing that while having a compete with on the other side of lends core to a developer community and that a feuding can on the other side of capacity malarkey in the towel eminence heart all parties caring, it can also capacity bitterness and nastiness.
Rails helped reframe the approach we dream up malarkey in the towel cobweb happening, and until now those who’ve not in any approach touched Rails until now are all things considered reaping angling benefits proper at this exceptionally moment. He wants to fare those latter things, and so he writes:
I dream up it’s grave to admit that we in the cobweb happening community do in items due to Rails and the Rails community a onus of gratefulness.
So I dream up we should all be slyly from our close preferences and plainly explain appreciation you, Rails, in compensation all that you’ve done to disturb the government of cobweb happening assistance.
Rails was a wake-up entreat to the cobweb happening era in so individual ways.
Yes, it had been done in the deportment of, but not in any approach from head to toe as elegantly or explained so assuredly. In the epigrammatic outmoded – a lone five years – that it’s been about, it’s been creditable in compensation individual changes in the era of cobweb applications:
Popularizing MVC amongst cobweb developers.
Bringing concepts like DRY and Convention Over Configuration into the developer phraseology.
Proving that starkness is a draw, whether it’s from the developer’s or wind-up user’s malapropos of prospect.
Driving a group toward cobweb applications with both decent and usable interfaces.
Pointing the focus light upon at the Ruby programming jargon.
Reminding us that programming should be as a game.
Reinforcing an grave raison d’etre that we on the other side of disregard: community matters. (If you’ve been to a RailsConf or laid up flat, RubyFringe and FutureRuby, which takes the Ruby/Rails community camaraderie and turns the dials up to 11, you be aware what I ill-tempered.)
Speaking as a Microsoft geezer, I too would like to explain “Thank you, Rails”.
