Content tagged with: rubyonrails
Ruby on Rails gives us M, V, C, routes and helpers. Some people add observers and concerns, among others. We’ve standardized on presenters. Service objects are gaining popularity. Uncle Bob wants you to add interactors, request models, response models and entities.
In the early days of a project, Rails absolutely dazzles.Tragically, the very same forces that make it so easy to add new features to a brand new Rails application are the ones that start to hold you back as the number of features grows. Your test suite gets slower and slower, and refactoring becomes more and more of a chore. Everything seems coupled together, and it’s hard to see much of a structure other than the MVC triad.
Ruby on Rails is huge. Even if you have worked with it for a long time, it’s unlikely that you have stumbled across everything yet. Do you really know what all of the built-in Rake tasks do? Have you seen all of the methods ActiveSupport makes available to you? Are you aware of all the queries ActiveRecord is capable of? Explores the extras of Rails and see if you can’t turn up some features that you don’t see all of the time, but that might just be handy to know …
Which web application development framework to use?. Simplicity, productivity, ability to deliver high quality of service (QoS), especially performance and scalability (can’t ignore that when you’re talking about 200,000+ users and expect high concurrency!) were our top criteria for framework selection. After considerable research on state-of-the-art, we zeroed in on 2 frameworks: 1) “Ruby on Rails” (RoR) for its super simplicity and productivity and 2) “Java Enterprise Edition” (JEE) for its obvious “enterprise” class, high QoS.
While Node.js is the hot new kid on the block, evented libraries like EventMachine for Ruby and Twisted for Python have existed for a long time. When does it make sense to use one over the other? What are the advantages and disadvantages to using node over ruby?
This video shows how to build a rocking’ mobile-ready site with Ruby on Rails. The presenter discusses his successes and failures, as well as how to get your site ready for every smart phone and tablet out there.
The Rails and Merb development teams merged to create Rails 3 in 2008, but while those competing teams merged, their frameworks didn’t. Though Rails 3 shows plenty of influence from Merb and its creators, today Merb itself is a legacy framework, with no clear, supported path for Merb apps to move forward to Rails 3 without significant effort.
This video discusses pattern matching. It explains how a pattern can be converted to a state machine, how to improve execution time of that state machine, and how to turn the state machine back in to a pattern. It shows how these state machines relate to the routing systems in Rails, and how we can use state machines to increase performance of the routing system.
This video presents the benefits of using Ruby and Rails at LivingSocial and the state of the Ruby community and Ruby in the enterprise.