While I agree that the "Rails mindset" is pervasive in the Ruby
community, certainly here in Europe I find many people are interested
in a more "plain Ruby" approach, augmented with practices from
functional programming.
The ROM project, the successor of DataMapper, is a good example. It
provides an alternative to ActiveRecord but based on the data mapper
pattern, so your models can be simple POROs. It's built from the
ground up on immutable objects, and hence most methods are simple
value-in value-out. The same people also made the IceNine gem which
makes it easy to freeze entire object graphs.
They use elaborate YARD documentation throughout their projects,
documenting the types that go in and out. While this is no substitute
for actual type checking, it certainly helps while coding to have this
implicit contract.
> --
> You received this message because you are subscribed to the Google Groups
> "Objects on Rails" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
objects-on-rai...@googlegroups.com.
> For more options, visit
https://groups.google.com/groups/opt_out.