comment on

One a friend of mine who's in sales and marketing said, "Java's great because its not programming.". Hmmmm. I don't think he was alone holding this notion.

XML could (is) suffer(ing) from much the same thing. I think that people are hoping that they won't have to analyze their information managment requirements. Instead they'll "Just put it into XML". Hmmm.

One the one hand it may be overkill for certain apps, on the other hand it is a nice way of storing information in a consistent and easy to parse format.

You're still gonna have to think about what it is that you're managing using XML and what you're gonna do with it. The more complicated your application environment the more effort its gonna require.

Randy's comments have encouraged me to revisit this for config files that I make. :)

In reply to RE: XML by jlawrenc
in thread XML overhyped (was: XML) by rodry

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks