Gradio Application about agency HOT 2 CLOSED

Okay here's what I'm thinking. I've decided to go with Gradio for now.

I did consider some other options. I'm new to these python data driven web frameworks. Here's a comparison table (AI created) that lists the main options I looked at:

It came down to Streamlit vs Gradio. The main reason being that they both support quick and easy prototyping.

Quick prototyping makes a lot of sense for supporting development of the library. I was hoping for the framework to be more capable of custom applications, but there needs to be a tradeoff. So customizability will have some limits but we always have options like adding new integrations or using the Flask/React app.

What tipped me from Streamlit to Gradio were mostly two things:

1. Oobabooga TGWUI
   I really want to build an integration with it. I think it would be great for both projects. Users could hook it up to interface with a network of agents connected through agency using the same interface that they use for training, etc. The integration could also become a source of feedback for development of the library.

2. Architecture concerns with Streamlit
   I have some reservations about the architecture of Streamlit. Gradio is more straightforward in that it uses regular http requests with callback functions. I'm assuming it will be easier to reason about if I need to debug something.

One area that I felt Streamlit wins is in hosting options but it's not enough to change my mind. It's easy enough to host a Gradio app if necessary.

Given that I'm settled on Gradio, I'll be jumping into coding. An initial version may not take long but bear with me.

Please let me know if there are any thoughts or concerns about this choice.

from agency.

Alright I just merged the Gradio app! Let me know if you find anything wrong!

#90

from agency.