Yes, please! I'm going to go back to struggling with my login form 😦

The idea is to have rules-based systems which know the requirements examining the system diagram and engaging with the engineering team to make recommendations - sort of like a system-level linter.... but also working at runtime, so a linter that can watch the system as it's running and try to see when it's violating it's own design constraints...

"self aware" computing FTW.

FTW indeed!

wtpayne, officially the most advanced user of htmx, probably ever

So the code needs to be updated dynamically?

Can you explain that part more?

It feels like you should be sending down a JSON object w/ data and the function, assuming it can't be run on the server side? But I need to reread all this.

Well ... eval seems to works OK

And it's early days on the advanced stuff.

One of my cofounders is doing the research for his PhD right now.

I'm just making sure we've got the tools in place for when he graduates.

So, there are basically two nested tags, The outer one is a div that gets swapped out when the rendering logic changes ... a component running on the developer's computer in the back-end detects when the source file is saved, and if it results in different output from before, the server will send an SSE event to the front end with the new display logic. Nested inside that is another element ... application dependent, but most likely an ... which gets updated by the display logic using data sent in a different SSE event. (But both are transmitted using the same connection ... the server has a primitive sort of pub/sub so the backend can specify which events should be published on which topics).

The server can be running on a different computer to the developer ... and the whole system can have multiple developers and multiple servers, depending on how it's configured.

Ultimately, the fragments of UI are just web resources being passed around the compute graph ... dictionaries that map resource-id to a (content-type, buffer) pair.

So these can be images, HTML, CSS, Javascript or whatever else you fancy.

I need to document this at some point, obviously.

But the end result (I'm hoping) is a system of legos that you drop into a graph, and somewhere else the UI magically reconfigures itself to show data from the new lego brick.

That's some really cool stuff @User. I 'm a systems engineer currently working a modular system of components for building front end UIs with specific design constraints and it works like legos much like you describe. So I'm real keen on seeing how what you're saying works. I also seem to be the first person to star your project on github. 🙂 Looking forward to seeing how it turns out.

Hey @refined-ice-80461 -- is your work open source? If so, I'd love to check it out 🙂

@User - I'm kinda figuring things out as I go at the moment, and systems engineers are a big part of my target audience, so I'd love to have a chat at some point.

@gorgeous-ghost-95789 It’s not open source yet but it will be. @future-boots-43048 sure thing any time

Dang I've been overthrown. My htmx project is currently on hold but I will return at some point with some outrageous requirements, I'm sure.

\> tfw an employee at your own company recommends svelte in the company slack

"I don't see how JSON violates REST"

the cigarette is laced with nitroglycerin

Today is "fight with people about REST on the internet" day

And what a pointless day it is!

I just call it "competitive advantage"