A Java Geek weekly 95

In defense of XML

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.

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:

  • Explore some of the reasons why the mighty XML has fallen
  • Raise some downsides of the popular alternatives
  • And describe how XML already solved those problems
"Bypassing" specialization in Rust or How I Learned to Stop Worrying and Love Function Pointers

I didn’t know about specialization, I’m glad I read this post!

Critical Container Registry Security Flaw: How Multi-Architecture Manifests Create Attack Vectors

Getting registry push privilege is a hard requirement for the trick to work. It’s a nice trick, though.

Policy-Driven Cost Optimization with Open Policy Agent and Kubernetes

Cost-optimization wasn’t on my use-case list for OPA, but it makes a lot of sense.

Writing a Technical Book for Manning

I’d would have liked to have been the one experiencing it. My experience with Packt was very different–and not for the better.

Deeper theories of program design

A very unusual article, but definitely worth reading.

git-branchless

git-branchless is a suite of tools which enhances Git in several ways.

+ * It makes Git easier to use, both for novices and for power users. * It adds more flexibility for power users. * It provides faster operations for large repositories and monorepos, particularly at large tech companies.

So many tools want to improve upon Git. I’ve to try some of them as some point and see for myself.

The Structure of a PDF File

I’m working on PDFs at the moment, and while I’m doing it at a higher level, it’s still very interesting.

API Standards ARE Data Standards

Very interesting point of view. I never thought about it.

Building Telemetry Pipelines with the OpenTelemetry Collector

I had to learn all the hard way, by reading the documentation and making mistakes. The post above is an amazing resource to learn about the OpenTelemetry Collector in one place.

Evolution of HTTP

Good overview of the evolution of the HTTP protocol, from 0.9 to 3.0.

What is X-Forwarded-For and when can you trust it?

TL;DR: It’s a mess! But the details on why it’s a mess are important.

Reverse Proxy Deep Dive Part 2: Why HTTP Parsing at the Edge Is Harder Than It Looks

Let’s continue this small series on HTTP with an article on reverse proxies.

Why Japanese Developers Write Code Completely Differently (And Why It Works Better)

The author is very enthusiastic, and I’m sure there are culture benefits. However, I’d have like measurable impacts.

Furthermore, my experience is that the Asian culture in general respects hierarchy first and foremost.

Nicolas Fränkel

Nicolas Fränkel

Nicolas Fränkel is a technologist focusing on cloud-native technologies, DevOps, CI/CD pipelines, and system observability. His focus revolves around creating technical content, delivering talks, and engaging with developer communities to promote the adoption of modern software practices. With a strong background in software, he has worked extensively with the JVM, applying his expertise across various industries. In addition to his technical work, he is the author of several books and regularly shares insights through his blog and open-source contributions.

Read More
A Java Geek weekly 95
Share this