I think that keeping things simple works better for most users, even though some advanced setups can give you better results or help with special projects like composite images. When you want to share your setup with others, simple is definitely the way to go.
ComfyUI should really add more basic features built into the main nodes. Things like basic math operations would be really helpful. It would also be great to have a simple way to merge upscaled inpainting results automatically, similar to how Automatic1111 handles it.
I just want to be able to use the software without having to install tons of custom extensions and troubleshoot compatibility issues. I don’t need every single detail to be perfect if it means waiting forever for results. My workflow is to get something that works well and then refine it step by step, sometimes even doing manual edits.
That’s just how I like to work with my art projects.
Completely agree. Switched from A1111 to ComfyUI last year and ended up downloading tons of custom nodes for basic stuff that should’ve been built-in. Twenty different extensions that all conflict after updates? Total maintenance nightmare. The breaking point was rebuilding a complex workflow from scratch after a node died. My quick temporary fix actually worked better and ran faster than the original. All those extra parameters just give you more ways to screw things up. You’re right about manual refinement too. I used to waste hours tweaking settings for the ‘perfect’ result. Now I generate something decent fast and clean it up in post. Way more productive.
The psychology of simple workflows matters too. When I started, I’d avoid projects because my setup was so complicated that just opening it felt overwhelming. I had this workflow with conditional branches and nested loops that produced amazing results, but I dreaded using it. I realized I was procrastinating because the tool had become harder than the actual creative work. Now I use dead simple chains I can understand at a glance. The output might not be technically optimal, but I actually finish projects instead of endlessly tweaking parameters. The best workflow is the one you’ll actually use consistently.
The complexity trap is real. I’ve watched teams build elaborate automation pipelines that take weeks to set up and break constantly.
What kills me is people chasing the most advanced setup when a basic one handles 90% of their problems. My colleague spent months building this complex CI/CD system with 12 different tools. I was shipping features with a simple script that did exactly what we needed.
Same thing here. You can spend forever perfecting a workflow or get something working in 20 minutes and iterate. The second approach teaches you what you actually need versus what you think you need.
Keep things simple and other people can understand and contribute. Complex workflows are write-only code - nobody wants to touch them when they break.
same here - i stick with simple setups for this exact reason. built some insane 15-node workflow once and it died after one update. now i use basic stuff and get good results way faster. the “perfect” setup usually isn’t worth the hassle when you can just fix things manually later.