In theory, the developers time is more expensive than the hardware.
It depends. If you can amortize the developer time across many projects through re-use, you can turn that around.
In this case, the ActiveRecord framework really needs to better support some of the things they’re trying to do. So working outside the framework, but doing the work so that it extends ActiveRecord to add the needed support lets the entire Rails community benefit.
Of course, there’s still the fact that only one person is paying for that, but then again, the developer time on this project is “free” (donated).
RE: Go with hardware by scottb :: NR7 :: Show
In theory, the developers time is more expensive than the hardware.
It depends. If you can amortize the developer time across many projects through re-use, you can turn that around.
In this case, the ActiveRecord framework really needs to better support some of the things they’re trying to do. So working outside the framework, but doing the work so that it extends ActiveRecord to add the needed support lets the entire Rails community benefit.
Of course, there’s still the fact that only one person is paying for that, but then again, the developer time on this project is “free” (donated).