Children, this is the picture of “XML”. Document Markup Language. It was used by the end of the XX-th century.
This was a post from May 2015. Unfortunately it is still actual in May 2018.
This probably applies to you. Especially if you are an Developer. Or if you suspect you might be a .NET Lemming? (A member of any large group following an unthinking course towards mass destruction)
.NET and SharePoint in particular are two likely offenders here. It is now 2015 (May) … Oops? It is already 2018, May.
This subject (XML in software development) has been reiterated to death. And back.
It is 2015 (or rather 2018) and there are (still) major development platforms with massive following (hint: Node.JS), using just JSON. There are tools (hint: Grunt, et all) using JSON. There are global concepts and platforms (hint: npm), using just JSON .
It is 2018 and software world has moved to JSON (no hints here). XML is invented (ages ago) and is designed to be used as Document Markup Language. Let me rephrase this: text format for describing document layout and content (hint: think of HTML). Did I already mentioned it is 2018? Well perhaps MSFT / Visual Studio, decision makers aka “stars of legacy Olympics” need to be reminded what year this is. As a side note.
I think I can speak for a vast majority of developers, when I say: Please do not make me “enjoy” Visual Studio XML editor and PLEASE, do not make me deal with configuration files like this one:
<!---These references should be considered "infrastructure" references and should be used exactly as described -->
<ReferencePath Include="C:\%ProgramFiles%\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\mscorlib.dll" />
<ReferencePath Include="C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\System.ComponentModel.Composition.dll" />
<ReferencePath Include="C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\System.Configuration.dll" />
<ReferencePath Include="C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\System.Core.dll" />
<ReferencePath Include="C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\System.dll" />
<ReferencePath Include="C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\Facades\System.Threading.Tasks.dll" />
<ReferencePath Include="C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\Facades\System.Runtime.dll" />
<ReferencePath Include="C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\Facades\System.Runtime.InteropServices.WindowsRuntime.dll" />
<ReferencePath Include="C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\System.Xml.dll" />
<ReferencePath Include="C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\System.Data.dll" />
<!---These references allow usage of WinRT APIs and constructs (e.g. WinRT events and async). -->
<ReferencePath Include="C:\Program Files (x86)\Windows Kits\8.1\References\CommonConfiguration\Neutral\Windows.winmd" />
<ReferencePath Include="C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETCore\v4.5.1\System.Runtime.WindowsRuntime.dll" />
I can not stand this little XML files dotted around Visual Studio 2017 projects. Long time ago, in Office 2003 this might have looked useful, but not any more. It does not look useful, and we know now it never was useful. Yes, yes, I know, I already mentioned which year we live in.
It is not just Visual Studio’s fault. VS already has very good JSON editor and a such. There are very large LOB platforms that MSFT makes which are still (yes in 2018) returning XML “nuggets” like this one:
<link rel="self" title="StaleMailboxDetail" href="StaleMailboxDetail" />
Above XML/Atom syntax, is a norm for Web Apps developed by MSFT in front of SharePoint. I am sick and tired of REST API’s returning XML. I really am. I want each of them REST API’s to return JSON.
And good old SharePoint is still one sorry mess of XML and XSL. Yes you read this right, XSL is used all around the place in SharePoint in year 2018. Ooops, 2018 … I said it again.
And the core argument is: This is because of Legacy clients (and servers)? Are we really to believe MSFT has no enough organizational and development resources to introduce JSON version for each Web Service and to mark XML “offenders” as deprecated? Or are we still to use and love XMLHTTPREQUEST, from Node.JS, as calmly used by some MSDN samples in 2018?
Darn, 2018 … I said it again…