You Must Program AI With XML

AI has been trained for markdown because it is a little bit fuzzy, and then for JSON because people got scared of XML.

But humans can't visually reason about JSON, XML is a text based concept map, JSON is a bracket soup.

Perhaps college kids got scared of what Java did to XML, of how name-spaces damaged the readability.

Who knows, it is their problem, you got an AI find a dog format around it and keep everything as XML.

Without XML the markdown and JSON combine to create liability, syntax goo, and useless unparable text that can only be used by AI.

With XML, you can read everything, translate upgrade, measure, and even use gold old fashioned AI to transform it.

But above all, XML gives you advantage over all the markdown and XML inventors, including corporations.

Take it, keep moving, and don't look back.

Do not ignore XML, the AI people were insane to use markdown and JSON.

Because I adopted it, I can invent new programming languages, both for declarative events processing and even web component programming.

And at the end of the day, I just ask AI to create XML application blueprints, and those are my stunning application templates.

Components, Event Sourcing, and Application Templates, all because XML is readable at scale and JSON is not.

I have created unspeakable wonders, and they are just my XML language tests.

That's how powerful XML is, your back of the envelope doodles are more magnificent than pro software.

If you use XML, you will start ahead of everyone else.

Some time ago, code that was largely public, leaked, and some cats looked at it and said it was a total mess.

Instead of being a little cry baby, I assumed that the mess, is the result of an advanced operation, a compilation for the age of AI.

I asked, what kind of system of things would generate this mess, it is obviously AI performing a translation from a pristine language, to a mess.

And the question was, is the pristine language just text? Does the AI decompile a winning mess into a strict application specification.

So that it can make wise and delicate changes, at the core, and then compile it self back into a mess.

Instead of answering this, I asked what would be higher and cleaner, and the answer was XML, a beautiful vocabulary that speaks intent, not jargon.

Intent says drag mouse, jargon says, on mouse down, take mouse move, until mouse up – yuck.

The declarative XML is in deed a beautiful language, that does speak human, with the added benefit of making text structural.

Today’s experiment revealed, that 60 lines of code, creates a swarm of four co-dependent agents, and generates any application.

XML is it, it is foolish to ever think otherwise, especially in an age where you can ask AI to make verbose XML beautiful

I am largely generating user interfaces, because beneath the user interfaces, it is just ifs and loops attached to XML that relies on Web Components.

And then the loops and ifs, iterate over a tree, but not an exhausting arbitrary, pull out of my cowboy hat tree.

It is a virtual file system, part of an tiny OS, where everything is a file.

If you want to emit an event to an application, you just write to its control file.

If you want to render a self updating list of users, you iterate over a list of files in a directory, server sends the files, from a databse.

They are ordered, because beneath the VFS, is just a simple XML tree.

I distributed logic so that by the time it reaches the user interface, you are just looping over some path.

I have functional reactive programming, in all the right places.

SO in the end it all falls down on the User Interface, it is bootstrap CSS backed Web Components warped in XML for readability.

When we write imperative code, programming line by line, we have to remember to free resources and we have to make a mess too.

When we dare to declare, this is what my pipeline looks like, we also get to say: stop, tear it all down.

And the active pipeline is just lists of subscriptions, the program has no trouble scaning over and removing them.

When we use the declarative approach, we don’t have to shape the program to be readable.

Programming languages often aren’t, they are mostly for computers and then a litte bit for humans.

A declarative XML blupeprint, just makes the sourcecode for humans, the runtime code for computers.

As it should be, IST NICHT FÜR DER GEFINGERPOKEN UND MITTENGRABEN! RELAXEN UND WATSCHEN DER BLINKENLICHTEN. - Ja.