Ruby on Rails: The Documentary
Interesting. history creating a framework for web applications in Ruby, which is mainly told by the creator of the framework, David Heinemeier Hansson. The framework itself for its time was really breakthrough - it increased the convenience and speed of development, allowed the developer to throw a prototype alone or even bring it to the product.
True, the product is on top of it. Ruby on Rails There were a few problems:
- performance When the application became popular and received an increase in load, the checks for the iron power used became inhumane.
- approach conventions over configurations This approach is about implicit decisions that are hidden from developers, but stick out in the form of some guidelines. And everything works great while all colleagues share and follow conventions. But as the solution and the team grow, someone comes along who, for example, uses metaprogramming. (Thanks, Ruby.) implicitly changes the basic behavior and our whole slender scheme breaks down and we need to spend time on non-trivial debugging. As a result, I personally bow to the mantra “Explicit is better than implicit.” The Zen of Python.
It is interesting that I first met with Ruby on Rails years 10 CS169 - Engineering Software as a Service by Berkley This course by the authors Very enthusiastically used Ruby on Rails as a basic framework
- promoted TDD. (test driven development) High code coverage
- learned to use BDD (behavioral driven development) And that's where I met the cucumber. (Cucumber) Since then, I have lost faith in this approach. (But it's a different story.)
- showing you how to use Capistrano I used this tool for some time in my production projects.
- explaining why code that looks like text in the language you're speaking is cool. I didn’t buy that part then or now. (Although the 1C would probably understand this explanation. n)
As a result, it was the production code on Ruby on Rails that I did not write much, but I saw how the concepts of this web framework penetrated into frameworks in other languages. (The same ActiveRecord pattern) And I was wondering where he went off the radar. In this documentary you will not find the answer to this question, but you will learn how this framework became popular. And not only David Heinemeier Hansson will tell you about this, but also a lot of other people who have had a hand in the development of this framework.
- Jason Fried, Founder & CEO at 37signals
- Tobias Lütke, Co-founder and CEO Shopify (member of the rail core team 2004 along 2008 year) Jeremy Daer, developer of 37signals and member of the rails core team 2005 year
- Jamis Buck, now in MongoDB. (member of the rail core team 2005 along 2007 year)
#Software #Engineering #History #SoftwareDevelopment #Architecture #SystemEngineering