I think JSON was circa 2006, but why pick on Maven when you could pick on NIEM, FPML or any other non-trivial data interchange standard. 

XML being "dead" has alot to do with cloud vendors refusing to support it in their offerings because cloud native and cloud migration is the flavor  du jour.

Which mean somebody at Google and AWS sat down, surveyed the enterprise landscape and decided organizations using XML shouldn't have a place in the cloud to put their data, simultaneously those enterprises haven't connected the dots and told them there ought to be a place where we can put our data because we are paying for this [expletive deleted].

Was that a commercially driven decision or one driven by a few overly influential engineers.

Does everybody who has XML data really want to have to convert it to JSON in order to be cloud native, or is there a latent opportunity for an enterprising vendor with an eye for a gift horse.

On Tue, Jul 20, 2021 at 4:32 AM Rick Jelliffe <rjelliffe@a...> wrote:

Is Maven a good example?  Maven was designed circa 2002 when XML was at its peak, which is 19 years ago.

(And JSON was designed only circa 2001 so the Maven developer may not have even heard of JSON by that stage.)

 

Rick 

On Tue, Jul 20, 2021 at 5:42 PM Mukul Gandhi <mukulg@s...> wrote:

I think that, some people within this thread, have expressed concern that usage of XML is reducing.

An example came to my mind. I'm sure, most of us and others as well, have used the Java build framework Maven which is hugely popular. Maven's build configuration is mentioned in the file pom.xml. I therefore imply that, Maven uses XML as a primary means to manage Java builds.

I'm sure, there would be many other examples of good XML use.

On Sun, Jul 18, 2021 at 2:07 PM Rick Jelliffe <rjelliffe@a...> wrote:

... 

--

Regards,

Mukul Gandhi