When I started my career, XML was ubiquitous. The meta-information in a Java JAR file — the manifest — follows a proprietary format. But Java EE designers built it from the ground up on XML: meta-information of all artifacts is in XML format e.g. web.xml, ejb-jar.xml, application.xml, etc.
When I started my career, XML was ubiquitous. The meta-information in a Java JAR file — the manifest — follows a proprietary format. But Java EE designers built it from the ground up on XML: meta-information of all artifacts is in XML format e.g.
Java EE is one example I experienced personally. But XML was everywhere in the enterprise world at the time. Its prevalence manifested itself in two areas: configuration and data transfer.
Ever since then, it would be an euphemism to say XML has been losing in popularity. Other formats, such as JSON and YAML, have replaced it in the hearts of developers. In this post, I’d like to:
I think there are several reasons that led to the downfall of XML. It’s not a single one, but the conjunction of them that led to the current state.
Associated with “Enterprise”
I’m afraid the worst flaw of XML is its close association with the enterprise world. As everybody knows, Enterprise is notoriously bad — by definition: bloated, heavy, not nimble, etc. And yes, that’s sarcasm if you wondered.
In general, perception trumps truth. Developers are no different in that regard. In the end, that’s how Hype-Driven Developers — and most developers, perceive XML nowadays.
The agenda of the talk included an introduction to 3D data, its applications and case studies, 3D data alignment and more.
Data Quality Testing Skills Needed For Data Integration Projects. Data integration projects fail for many reasons. Risks can be mitigated when well-trained testers deliver support. Here are some recommended testing skills.
A data expert discusses the three different types of data lakes and how data lakes can be used with data sets not considered 'big data.'
The first step is to understand what is data governance. Data Governance is an overloaded term and means different things to different people. It has been helpful to define Data Governance based on the outcomes it is supposed to deliver. In my case, Data Governance is any task required for.
Data Observability: How to Prevent Broken Data Pipelines. The relationship between data downtime, observability, and reliable insights