Kurt Stephens

Links about Caching in Rails.

• Object Caching in Rails
• CachedModel
• acts_as_cached
• ActiveRecord Explicit Caching

• “Expanded Caching Scope” – http://ryandaigle.com/articles/2007/2/21/what-s-new-in-edge-rails-expanded-caching-scope
  

http://eigenclass.org/hiki/Changes+in+Ruby+1.9

Excellent synopsis of changes to Ruby 1.9.

Other goodies:

http://eigenclass.org/hiki/non-synthetic-benchmarks-for-yarv

http://eigenclass.org/hiki/porting-rails-to-ruby-1.9

Here is a patch to rcov 0.8.0.2 to rethrow any exception generated by the scripts to be traced, after report generation (most importantly SystemExit). This allows the exit code from test runners (like spec) to be used under rake.

Huh?

http://youtube.com/watch?v=asnVcbWQ2cg

Wow. I think I vaguely remember this. Wish I hadn’t.

• Omissions in UML 1.5 spec acknowledged – http://www.omg.org/issues/issue5907.txt

• Cites UMMF – http://www.cs.kent.ac.uk/pubs/2003/1733/content.pdf

Advice is a programming construct from the Lisp world that pre-dates aspect-oriented and object-oriented programming. Advice is code that is placed before, after or around an existing function’s body. Examples of advice can be seen in Emacs: in Emacs Lisp, the advice is specified with macro syntax that expands to lambdas.

Wrote this (err… something similar at work :) in Ruby just before I found http://aquarium.rubyforge.org. The advice bodies are bound as methods using Class#define_method with a Proc; the advice has access to privates.

It provides simple :before, :after and :around advice objects that can be applied to and removed from multiple instance methods on multiple classes. It’s not AOP because there are no point-cuts patterns, but it is a bit more object-oriented than a typical Lisp advice macro.

See Aquarium for more industrial-strength AOP-style programming.

Cool new Ruby gem Aquarium – AOP framework for Ruby:

http://aquarium.rubyforge.org

Discussion of AOP, Rails and GOF design patterns:

http://cfis.savagexi.com/articles/2007/09/05/rails-unusual-architecture

Not really AOP or Decorator because it occurs at the M1 (class, module) and not the M0 (object) meta-modeling layer.

http://www.scienceblogs.com/loom/2007/08/06/branded_with_science.php

http://sciencetattoo.com/