u/AetopiaMC

I find this internal implementation detail quite interesting and wonder why was this decision made since JavaScriptSerializer directly maps JSON to a .NET object or vice versa.

With DataContractJsonSerializer, it maps JSON to XML before actually giving a .NET object.

Now I assume this was done due to:

• SOAP being popular during the 2000s with XML being preferred.
• The JSON to XML mapping just helped with implementing JSON serialization quickly.

Aside from that, are there any other reason(s) for this design decision?