Comment by christoff12 | Hacker News Reader

Comment by christoff12 | Hacker News Reader

Parent Full thread

How would we rate this revised version on a scale from 1-10?

"""

Totally fair. You can build the first 10-minute demo with an LLM now.

The hard part is usually what comes after. You need editable state, templates, and email-safe HTML. Then come export pipelines, custom blocks, permissions, and all the rendering edge cases that show up with real usage.

AI makes structure more important, not less. That’s why we launched Unlayer Elements. Instead of having an LLM generate a static blob of HTML, it can target structured components that map back into an editable email, web page, or document.

So I'd use AI to prototype it. I'd use Unlayer when that content layer becomes production infrastructure you don't want to maintain yourself.

"""

I made a deslopper[1] tool based on a new skill[2] I saw on twitter earlier. It's still a little smelly imo, but better.

---

[1] https://deslop.btst.workers.dev

[2] https://github.com/petergyang/no-ai-slop

To be blunt, I would rate it a 1, a 0 if I could. I would stop reading after the third sentence. FWIW, humanizers do not work. Can they make AI text sound better - yes, but only mildly. Also, they won't trick good ai detectors, and the resulting text is still cumbersome to read.

This is what I got first time with a humanizer I built, still sounds terrible:

"Yeah, an LLM gets you the 10-minute demo now.

The expensive part is everything after, once real users depend on it. You end up maintaining editable state, templates, email-safe HTML, export pipelines, asset handling, permissions, custom blocks, and live previews. That takes months.

Structure makes AI output usable here, and it gets more important as the workflow gets automated. That's the idea behind Unlayer Elements. The LLM generates real editable components that map back into the actual email or page, and you keep editing what it makes like anything else in the tool.

I'd prototype with the LLM. I'd bring in Unlayer once that content layer becomes real infrastructure you don't want to own yourself."

Thanks for the candor.

My version, off-the-cuff:

""" Making a demo that does some things is easy. Making a demo that does all the things is hard.

We took a lot of time to make this product polished. We nailed down a lot of UX gotchas and a lot of bugs that come from poorly written back-end code.

If you don't need the polish, then a demo is more than sufficient. We built this for those who just want to ship, not fight with their agent about tech stack stuff. """

Reply on news.ycombinator.com