4 ms·
It’s open source. The only way to compete is on your merits in open source. If you want another UI to flourish, clone both it and A111, copy and paste the bits
by ShamelessC 3y ago
It’s open source. The only way to compete is on your merits in open source.
If you want another UI to flourish, clone both it and A111, copy and paste the bits from A111 you’d like to have in yours (with attribution) and push it up along with any features you personally want.
That does require developer time, and developers may converge on a popular implementation with good tests and lots of features as it’s easier to contribute.
The bottleneck isn’t really the community though, it’s the developers.
- brucethemoose2 3y agoIts not that simple, as A1111 uses the old stability AI implementation while pretty much everything else uses HF diffusers code. I worked trying to add torch.compile support to A1111 for a bit, fixing some graph breaks locally, but... It was too much. Some other things, like ML compilation backends, are also basically impossible.
- Filligree 3y agoDo you know what it would take to support longer prompts with HF? The 77-token limit is what's so far stopped me from making the jump.
- brucethemoose2 3y agoIts super easy, in fact I think they specifically have a long prompt pipeline. Look at the implementation in pretty much any diffusers UI (like VoltaML or Invoke) Facebook's AITemplate backend even supports long prompts now.
- emikulic 3y agoWhat benefits does the Huggingface diffusers(?) implementation have over A1111?
- brucethemoose2 3y ago- Compatibility with stuff from research papers and ML compilers since it is the "de facto" SD implementation. - The codebase is cleaner more hackable, and (compared to base SAI code) more performant. - HF continues to put lots of work into optimization and cleanup. For instance, they ensure there are no graph breaks for torch.compile, and work with other hardware vendors for thier own SD implementations.