In irb (and hence, script/console), an underscore is a kind of global variable that holds the last result.
In irb (and hence, script/console), an underscore is a kind of global variable that holds the last result.
What we found should be generally applicable to all Rails applications, so I’d like to share them:
* Don’t use ActiveRecord#attributes or ActiveRecord#read_attribute
* Get your :includes right
* Don’t check template timestamps ( cache_template_loading = true)
* Don’t use url_for
* Don’t let Rails parse timestamps
* Don’t symbolize keys (local_assigns_support_string_keys = false)If you interested in the nitty-gritty details of each change, keep reading!
Remember: ugly, buggy and slow aren’t enough to make users think it sucks enough to switch (think MySpace and Windows)
Plumber is a Proc leak-detector. It automatically hooks into your controllers and reports, for each request, how many Proc objects were garbage collected, how many were created, and how many survived from the previous request. It also reports where each Proc was created and shows you how many were created at each location. The report gets written to a file in the log/ directory, named “objects-#{pid}.log” (where #{pid} is the process ID that is running your application).
Whenever I tweak my website design, a yellow form field background often fills up some (not all) form fields in my web browser (both IE and Firefox). I tried tweaking the site CSS and tried all sorts of form field tweaks, but the Yellow Form Field Background would just not go away. I am sure the yellow form fields bugs all web designers too. I finally identified the cause… Yellow Form Fields I identified that the cause of the yellow form field background was the Google Toolbar
A fast web crawler that stays on the site it started from. Crawler randomly picks a URL from the page retrieved and follows it. If can’t find a URL for the next page, Crawler starts over from the beginning. Crawler is multi-threaded and can run as many threads as you choose.
