Hacker News Reader

Comment by swiftcoder | Hacker News Reader

> I always hated Comfy's node based UI

It's one of the most uniquely hostile user experiences I've ever had the (dis)pleasure of working with

Awhile back I built a project which reads comfy's API and builds a typescript sdk from it. Much nicer to work with and still benefits from node caching and the comfy ecosystem. Perhaps I should clean it up and open source it, though I haven't looked around and there may already be other projects doing this out there.

Using AI for the ComfyUI API or workflows worked pretty well for me even early this year.

However, today I don't see a reason to use ComfyUI at all.

For Qwen Image 2.1, I had Opus 5.5 create a backend outside of ComfyUI and it was able to make generation take 20% less time with some optimizations.

The optimizations it implemented were caching the text computation in Qwen Image 2.1 rather than including it in every step, fusing projections into a larger matrix multiplication, and decoding the VAE in horizontal bands or something like that.

If there was anything interesting in ComfyUI nodes, I imagine I could just have the AI adopt the relevant code instead of dealing with ComfyUI or custom nodes.

I remember precisely how ComfyUI started, and the motivation was something along the lines of "look at the cool guys working in Houdini and Resolve, they must know something" (I wish I was kidding). Of course nobody thought that DAGs are just poorly suited for the task, even when plugin authors started trying to slap loops on top of them shortly after that.

Reply on news.ycombinator.com