On Tuesday 27 December 2005 12:11 am, Gregory B. wrote:
On 12/26/05, basi email@example.com wrote:
Ruby for Rails looks like the book that will satisfy my current
craving. Any chance an electronic copy is available for purchase?
I have a big problem with a few sentences in the preceding URL. Or at
I understand them. They seem to be advocating getting rid of config
putting all logic in code, at least my reading of the following quotes:
“A full Rails application probably has less total code than the XML
to configure the same application in other frameworks.”
"Rails strives to honor the Pragmatic Programmer’s DRY Principle by
the extra work of configuration files and code annotations. You can
in real-time: make a change, and watch it work immediately.
Forget XML. Everything in Rails, from templates to control flow to
logic, is written in Ruby, the language of choice for programmers who
get the job done well (and leave work on time for a change)."
Putting all your logic in code is nothing new. That’s how it was done in
60’s. By the 80’s programmers created configuration files so that a
request for increasing the customer number field from 5 to 6 digits
require recoding – the user could change the config file. It requires a
more coding, but it makes for a much more resiliant application.
Anyone can write a “simple” app if he or she puts all the logic in code,
that programmer will be called every time a change is needed in that
even if the change is trivial.
To me, the art of programming is anticipating likely changes and needs,
putting facilities for those changes and needs in config files, so that
change can be made with a simple tech support call instead of a code
I believe in data centered programming.
Once again, perhaps I misunderstood the intent of the web page, but if
advocating moving logic from data to code, that’s some advice I will not