I would be very interested to get a comparison from someone who understands the terrain.
I would be very interested to get a comparison from someone who understands the terrain.
The kernel is not robust to the stupid things I naively ask it to do. Often my code makes sense to me, but OpenSCAD refuses to create an object.
Performance falls off a cliff. You can work around it by pausing previews and adjusting resolution, but that’s a big UX compromise.
Still, I’ve tried a few other options and keep cycling back to OpenSCAD. The barrier to entry is very low, coding AI does a pretty good job, and there’s a decent ecosystem of community modules.
By the time you get done explaining the meaning of your schema, you might have run out of context. Not that it would matter either way. I've never seen the attention mechanism lock onto more than ~10 hard constraints at a time.
Not everything must be done via LLMs themselves. You could use one or more tools to help generate parts of the query.
You might be interested in this:
https://www.pedronasc.com/articles/lessons-building-ai-data-...
Yes, it would seem post hoc feature tree requires the constraints that come from context in your head, but I could imagine that for most cases a "drafter's intuition" in AI may be sufficient, and you could build an interface to allow that to be mostly given up front and then through iterate post generation.
I could imagine the stepwise approach may allow AI training to be more constrained / efficient that trying to do the whole thing in one go.