XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [xml-dev] How to design XML to have broad utility and yet alsoenable efficient application processing?

============
However much this list may despise them, namespaces are pretty well baked
into the political landscape of XML standards development.  I doubt
they'll go away in that context

Thanks,
Simon St.Laurent
http://simonstl.com/
================

One Footprint makes a line ...
I personally dont get the big hubbub about namespaces==evil.
I understand in well too much detail how awful it is and how it makes everything hard and how newbies fall over themselves (I did )
but in the end ... is it really harder than in java having to do 

    System.out.println("Hello World");

when in C I could do :
    printf("hello World\n");

< yes spare me the 1000x over details about how different this is>

In the end I dont find namespaces a big deal.
You either use them and learn them, or you dont and you dont.
If your job is being forced to suck in XML that has namespaces then you learn how to use them.
If not you blissfully ignore them.

"Whads Da big F'n Deal".
Writing good software takes work, there is no holy grail of "No Code Needed" or "No Brain Needed".


-David



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS