avatar
Jack @jackhpeterson.com

Although it's simple, it required me to build several "libraries" to make it work. - idempotent html getter/setter library. (required for hydration) - unified JS event/microtask/frame library. - simpler DOM change event system. - JS graph library for performance. (IMO, over optimized, already fast.)

aug 23, 2025, 5:14 pm • 0 0

Replies

avatar
Jack @jackhpeterson.com

I built several demos. Simplest concept: codepen.io/JackHP95/pen... - Parsing `Jack` would essentially run this JS: `o_.user.name = "Jack"`. - Running `o_.user.name = "Lea"` would update the HTML to `Lea`. That's the whole idea.

aug 23, 2025, 5:14 pm • 0 0 • view
avatar
Jack @jackhpeterson.com

Loose theory/example on how custom plugins would work: codepen.io/JackHP95/pen... I never really finished it because I got burnt out on for-loops and got stuck thinking about writing all the docs. Might pick it up again if there's enough interest.

aug 23, 2025, 5:14 pm • 0 0 • view
avatar
Jack @jackhpeterson.com

Working titles were `adios` and `buck.js`. github.com/jackhp95/buc... - Adios was an anagram of `as, is, do`. `[o-as="is"]` and `[onevent="do"]`. I realized the state update `do` wasn't relevant. It was all about lossless templates. - Buck `$` was initial namespace for the global state object.

aug 23, 2025, 5:14 pm • 0 0 • view
avatar
Jack @jackhpeterson.com

Yes, I know you lose an `s` in the anagram. It was a working title. It was also a way of saying goodbye to the typical FE framework conventions.

aug 23, 2025, 5:17 pm • 0 0 • view