What is going on in the land of ComfyUI

Beware, rant ahead!

Since a couple of days I am trying to get back up and running. Bootstrapping here and there, but I have a feeling this is not gonna go down well...

I started using ComfyUI about 5 - 6 months ago. At first it was very complex and the learning curve was steep.

Then I got comfortable and even started creating some custom nodes of my own. Creating workflows, with production in mind. Having a great time.

Then came Subgraphs. Released absolutely prematurely. But thank god, we could just not use them.

Now we're facing multiple issues at once. My proven workflows don't run anymore, because VAE Decode keeps crapping out. Ok, found a fix, just add a clear VRAM in-between kSampler and VAE Decode and even ZIT runs.

But now we have very popular custom node packs endangered by updates. KJ-Nodes throws errors, Rgthree put's a note into the console, that there will not be time to fix the node pack for Nodes 2.0. Almost no node pack is compatible with Nodes 2.0.

OK, it's tagged BETA (only after push back) and we can skip using them. But how long until it's the standard?

"Quo Vadis" ComfyUI? Will you make a stable branch that wen can update for fixes, but no features added, and make an experimental branch, for the "I feel lucky today" folks?

Or will you keep destroying working setups by prematurely releasing mandatory "great new features"?

Sorry for this rant. Sorry if I am stepping toes here. But I have just spent three days to get back up and running and there's no end in sight. And now I can't even go back to i.e. 3.68, where everything worked, because of the security hole the ComfyUI Manager created...

I am aware that updates are needed for newer models to run (ZIT), but why do those updates make SDXL, FLux, VAE Decode (Tiled and regular) crash beyond repair? Why do we need Nodes 2.0, when the ecosystem is not ready for it? Fancy, or needed for stability, speed and reliability?

There has to be a better roadmap imho.

Love you. Love ComfyUI. Want to keep loving it. But right now, this is a tough call...