3 ms·
Thanks for checking out HJX! A bit of backstory: I started building this after noticing how much context switching LLMs do when generating UIs across HTML, CSS
by loayabdalslam 8mo ago
Thanks for checking out HJX!
A bit of backstory: I started building this after noticing how much context switching LLMs do when generating UIs across HTML, CSS, and JS. Instead of three syntactic domains, HJX tries to unify structure, style, and interactivity into a single block-based syntax that still compiles down to plain HTML/CSS/JS.
Right now it’s an early prototype with a basic compiler design. I’d love to hear:
- Does this unified syntax reduce token/context fragmentation for AI models?
- Any suggestions on grammar design or compiler targets?
- Use cases you’d want to see supported?
Happy to iterate based on feedback.
- verdverm 8mo agoWhy do I want a bespoke language generated by an Ai, as compared to JSX + tailwind which I see as basically the same "html/css/js" without context switching (all in the same file), and something the Ai have seen significant amounts of during training? If I use something bespoke, then I have to do in-context learning, so am I really saving tokens in the long-run? (before we even get to more frequent failures / hallucinations that come with the bespoke)
- loayabdalslam 8mo agoActually, we're not like JSX; we offer a capsule solution. I can't show you my complete vision for the project right now, but if we could create a code generator using that language, it would be about 1000 times faster than normal because everything it generates would be in one place, in one way, and with one method, without retraining—just one agents.md file explaining the language.