And I called the programming framework Hullabalo (it is a good start), I am not sure what it means, but I think of it as a luxury framework.

This system is as powerful as wonderful, and it is already well documented, and just looking at the sample code, and matching up names properly wows.

It includes a dialect of the filtergraph, which is a programming language, that accepts input, transforms it, and sends it out.

The data sent out is under a label like, email:valid, so you can begin the next transformation procedure.

Here however, the input can be a button that sends something, or a web page input box, Signal to be precise.

So it is just like I promised, a surface, flat and shiny, on top of which you build data transformation networks.

Data in this program is sent around through events, anything can be an event, passwordFailure, appointmentReminder.

But as events occur in time, they can pass you by, so I decided, that an event must be captured by a signal.

AI insists on calling signals values, I suppose they are, values that announce when they change.

I call it event capping, an event capped with a signal, can never pass you by, you just look at the signal value.

So beneath are events, but on top are signals, and this program embraces that.

I give you a persist feature, and here you just name your signal, and when you reopen the browser the signal value will still be there.

AI can give persist any number of storage strategies, files, database, PouchDB, ORM – you just name the signal you want to keep.

Filters are how you program everything, it is a visual programming language, described in text, all your JavaScript functions/methods still live in the Plugin.

And shockingly, they are not twisted.

In my wisdom, and we have to call this wisdom, the Hullabaloo filters are the fourth generation of my filter programming language.

It took three powerful versions, for me to notice, a filter is just a function, it accepts a packet and return a transformed on.

This is very scary, a flow based programming language, that uses normal functions will make people sad, for the battles they had.

When they realize that they can use a signal as an output, and then those signals can be configured to persist.

And then, that signals can be created on demand via autoSignal, a causality violation from their perspective.

It all comes together, and all else goes to the heck in a hand basket.

The persist feature that allows you to turn off your computer, and still retain your Signal data, is where core programming ends.

What follows, will be luxury plugins, and seriously, the first one that comes to my mind, is a browser based file system.

Then an AI chat like user interface component, inspired by terminals, and done rather well by now defunct Mozilla Ubiquity.

This means, you can now send commands to the filters language, you will have a command event that executes functions in your application.

The user interface problem turned out to be a nothing burger, but I have to admit, it required four nearly separate features.

Regions, buttons, binding, and content, and probably still needs a fillout feature.

A luxury feature that is not part of the core, will convert objects to forms, forms to user data, user data to signal.

Luxury in the sense that it is a little excessive, not that it costs any money, the program is under MIT license.

You can see how a user interfaces are challenging, and they really need to be generated based on simple objects.

Those are transformation operations, perhaps best left for the filters language, and a rather glorious tutorial.

It is a good time to take break from programming, though at the same time, what isn’t a break in the age of AI.

And thank goodness, for that.

By the way, I know they say the devil is in the details, but that only holds true, if you don’t use reactive flow based programming and cheerful little signals.