- How much of this is vibe coded? The widget demos about halfway down seem half-baked; the currency input allows letters and letter inputs visually disappear when you unfocus it. The calendar input appears to select the day before the one I clicked. The markdown editor places hashes after the text on the current line rather than making the current line a header. The dropdown search doesn't seem to work (typing "R" shows React and AngulaR, but typing "Re" doesn't show any options).
All of those are fixable of course, and the idea is neat! It's just a bit of a rough showcase, at least on Firefox.
by recursive
2 subcomments
- All the field relationships seem to be expressed in strings. This suggests that you might not be able to use auto-complete or build-time syntax or type checking on them. I like the general idea, but that would be a big downside if I'm understanding correctly.
by rich_harris
1 subcomments
- The docs don't appear to cover progressive enhancement. Is this an oversight?
- Wonder why some technical decisions were made. E.g. i can make a dynamic form builder with Zod in ~1 week without AI. Why not do that? Why a custom engine?
- As someone just starting out with the JS ecosystem, how does this compare to something like SurveyJs?
by todotask2
1 subcomments
- Why did your release jump from 0.17.0 (2026-06-08) to 1.0 in such a short time?
If I use Tailwind, BEM or Boostrap, how hard it will be to customise? Flowbite have a few pre-made UI.
Shoelace UI is based on Web Components, now that it got bigger:
https://webawesome.com/docs/components/
by lanycrost
1 subcomments
- I always prefer declarative ways over all others, looks good to me!
- Ok, I love it.
Can you simplify how form dynamism works? I skimmed the docs and saw 'states', but it didn't immediately click how it works.
Do we build a tree of rules outside of the components? Are states attached to each component, bottoms-up, and then the form tree is managed by the library?
by charucharu
1 subcomments
- How do you handle schema migrations? If someone has thousands of JSON form definitions stored in a database and the component API changes, is there a migration strategy or versioning system built in?
- This looks very much like many slopped up UIs I've seen over the past few years. Not saying the code is, but the design itself looks vibe coded?
by mring33621
1 subcomments
- Lots of my previous employers had "data structures to forms" tech. It's very useful.
GolemUI looks like a nice open source version of this idea.
Thank you!
by vivzkestrel
0 subcomment
- no direct support for svelte is a major turn off
- Date range picker doesn't work...
by typeofhuman
1 subcomments
- Is there no file input type?
- How is this a new paradigm?
This idea for JSON -> form has existed for a decade, one example: https://github.com/eclipsesource/jsonforms
- Why the name Golem?
- The overuse of blue and purple gradient fills on the landing page is a telltale sign of AI slop.
I’m sorry, maybe it’s shallow, but that makes me close the tab.
by hungryhobbit
0 subcomment
- I knew this would be yet another garbage copycat library the moment I saw "new paradigm" in the title. When I actually looked at the webpage, I found I was not at all wrong.
P.S. I genuinely don't want to hate on the work of motivated devs, creating something useful for the community, and trying to share it. That's a great thing, and we want more of it!
But when some asshat comes in with an ai slop library that's redundant with a dozen other solutions (all of which people actually use in production to solve problems) ... and claims that they are creating new paradigms ... it feels to me like that makes things harder for every real new contribution.
All the stuff we want is signal, and crap like this just adds ego-based noise that blocks the signal.
by pooplord7
1 subcomments
- [flagged]
Hacker News