And it's done
https://wok.oblomov.eu/tecnologia/google-killing-open-web/
If you spot any errors (e.g. in my recall of history) do let me know. If you know of additional additional (direct or by proxy) examples of the war of Google on XML, RSS and/or XSLT do let me know.
If you know of more interesting use cases for XSLT, do let me know.
Also, I'll probably add a post-scriptum in the coming hours or days, but I wanted to get this out now.
#Google #openWeb #indieWeb #XML #XSLT #selfHosting #RSS and many others
History seems to (almost) repeat itself, so reprising my *2008* piece "Does anybody here remember Artie Eff?" https://nxdomain.no/~peter/does_anybody_here_remember_artie_eff_2008.html #ooxml #xml #documentfoundation #documentformats #libreoffice #opensource #libresoftware #freesoftware #microsoft #office @tdforg
Oh, quelle surprise #whatwg a fermé la discussion sur le ticket concernant la suppression du support de #XSLT. Le roi est nu. Depuis des années, les grands éditeurs de navigateurs se sont évertués à dégrader le support de #XML sur la plateforme du #web. Il n’est plus possible de le cacher. https://github.com/whatwg/html/issues/11523#event-19173131784
We don't need more. We need less.
Every week: A new framework.
A new "layer".
A new AI wrapper.
A new YAML format to abstract what used to be a shell script.
And then we wonder:
"Why is our software hard to debug?"
"Why do our builds break randomly?"
"Why is onboarding a 6-month journey through tribal folklore?"
I once said I write bug-free software that can be finished.
People laughed, especially product people.
Not because it's wrong.
But because they’ve forgotten it's possible.
We build complexity on top of confusion:
A + B becomes C.
C + D becomes E.
Now, E is broken, and we would create a new layer, but nobody knows how A or B worked in the first place. For example HTML/JavaScript, we leave it there and just add layers around it.
Take XML.
Everyone says it's ugly.
But you could validate it automatically, generate diagrams, enforce structure.
Now we're parsing YAML with 7 linters and still can't tell if a space is a bug.
Take Gradle.
You can define catalogues, versioning, and settings, but can't update a dependency without reading 3 blogs and sacrificing a goat.
This is called "developer experience" now?
Take Spring Boot.
I wouldn't trust a Spring Boot or any java Framework powered airplane.
Too many CVEs. Too much magic. Too little control.
We don't need "smarter" tools.
We need dumber, boring, reliable defaults.
Start boring.
Start small.
Then only change the 1% that needs to be fast, clever, or shiny.
You'll rarely even reach that point.
Like everyone says, "Y is more performant and faster than X", but no one reached the limit of X. Why should I care? Meanwhile, we use performant AI.
Real engineering is not chasing hype.
It's understanding the system so deeply that you no longer need most of it.
We've replaced curiosity with cargo cults.
We've replaced learning with LLM prompting.
And somehow, we're surprised when AI loses to a 1980s Atari in a chess game.
At least the Atari understood its own memory.
Simplicity = less maintenance = fewer bugs = happier teams.
We need less. Not more.
#devex #simplicity #softwareengineering #nocodependency#stopthehype #bugfree #springboot #gradle #xml #yamlhell #boringisgood #minimalism #AIhype #infrastructure #cleancode #pragmatism #java #NanoNative
Google started a WHATWG discussion for removing XSLT. Google has done their best to remove good tech from standards many times.
Responders raised issue with the motive for this change, as opposed to upgrading from XSLT 1.x to 3.1 which would fix all sorts of issues, etc.
Any posts that brought up Google's history and motives were marked as off-topic, and the thread was eventually locked by WHATWG.
Yet another cool and useful package from @coolbutuseless: {minixml} lets you build xml files in a programmatic way. I see good use for it in one of the internal packages at work... https://coolbutuseless.github.io/package/minixml/ #RStats #XML #cool #useful