in reply to Re^2: More than one way to skin an architecture
in thread More than one way to skin an architecture

Yeah. I generally agree with that statement. I also like Jethro's comment about maintaining the data in a human readable form (YAML comment above). I'm now thinking that persistence in a human readable form is the real need.

The value of all this, at least to me, is that I get to sound out the questions against a body of people who can give me some answers and act as a sounding board. My wife just can't answer these questions.

For that, I thank you all.

  • Comment on Re^3: More than one way to skin an architecture

Replies are listed 'Best First'.
Re^4: More than one way to skin an architecture
by BrowserUk (Patriarch) on Mar 19, 2008 at 05:31 UTC

    If you go the human readable route, take a close look at your options before commiting. Personally, I don't find YAML easy to follow or maintain.

    By way of example, here are the outputs of a moderately complex randomly generated structure from 3 contenders: Data::Dump, Data::Dumper and YAML. See which you understand best, and prefer to maintain.

    I also think that human-readable is a double-edged sword that should only be weilded if there is a definite need.

    Read more... (10 kB)
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]

In Section Seekers of Perl Wisdom