django-money VS gradio

I know this is not point of the article but:

> The PR was bigger than what I felt I could sensibly review and, in honesty, my desire to go through the hours of work I could tell this would take for a project I no longer used was not stellar.

The PR: https://github.com/django-money/django-money/pull/2/files?di...

Do others share this sentiment?

This doesn't look like a particularly big PR to me, judging solely by the amount of code changed and the nature of the changes at first glance.

Are most of your PRs at work tiny, couple lines of code at most? Am I sloppy for not even consider reviewing this for "hours"? Are all code bases I have worked on sloppy because features often require changing more code than this?

Currently I'm storing prices as django-money field but now I'm questioning the benefits of it and considering just storing prices in USD cents by default since the payment providers are handling currency exchanges anyway, what's your take on it?

Da du ja Django benutzt: Benutz auf deinem Model DecimalField oder Django Money wenn du es etwas high-leveliger haben willst.

oh, thank you, I have bookmarked this, page, will come in handy later, thank you!

There's also that library all the AI models started using that gives you a public URL to share. After researching it: https://www.gradio.app/ is the link.

It's used specifically for making simple UIs for machine learning apps. But I guess technically you could use it for anything.

What is the business model for https://www.taipy.io/, https://streamlit.io/, or https://www.gradio.app/? These are nice tools - but how will the sponsoring businesses support themselves? I didn't see any mention of enterprise plans, etc. Is the answer simply that "we've not announced our revenue model yet"? What should one expect?

Repo : https://github.com/gradio-app/gradio

There's TensorFlow.js for running machine learning on JavaScript, but personally, I'd prefer using the Python Gradio package, which is designed for creating UIs for machine learning inference demos.

I found an issue on gradio github but looks like it's closed so I am not sure if it's still a common issue or only I am facing it due to certain settings/absence of a fix. ( https://github.com/gradio-app/gradio/issues/3060 )

I disagree hard with this – for instance I've recently needed to dig into the code for the Gradio library, and when PRs are like https://github.com/gradio-app/gradio/pull/3300 (and the merge commit's message is what it is) it's hard to understand why some decisions have been made when doing `git annotate` later on.

Gradio for a ui that your commanderGPT can visit and use

gradio is documented, it doesn't seem very complex, it would be something like moving this block under the other one. i think it's ui_extra_networks.py, the file you are looking to edit. (if you do it make a copy to restore when you go to update)

Gradio did have an issue for a while where your URL was guessable, so unless you had a password it was pretty easy to find, but as far as I know they've increased the complexity so much that it's no longer an issue.

My script wouldn't work on the langchain because it was literally made within the gradio "docs builder" script that afaik was made specifically for their website (repo)