(Note: I work at Posit, but not on the Positron team)
748 karma · joined May 13, 2016
(Note: I work at Posit, but not on the Positron team)
I can remember an example where I suggested automatic treatment of missing values in a stats library, and the library maintainer disagreed. Meaning, my lobbying for Julia to do what R/Python did was seen as "Yes, but that's wrong and we shouldn't promote that sort of treatment". As a business user, I didn't care that it was theoretically wrong, the maintainer as an academic did.
That ends up becoming open-source prerogative. I could do it wrong "on my own time" in my own code...doesn't make either a bug, but a different choice based on perspective.
Thanks, glad you found Streamlit useful! The plan (per the link) is that Streamlit will continue on as an open-source project.
While I cannot speak to your experience with either project, I do want to point out that open-source doesn't have to be a zero-sum game. Gradio has different goals than Streamlit, which has different goals than Flask and Django.
In the end, congratulations to both HuggingFace and Gradio, Streamlit looks forward to seeing what they end up building!
The easiest way to have a secure Streamlit app would be to use Streamlit Cloud, which is https by default:
If you want to use some other combination of technologies for hosting, we've created a Deployment Guide to aggregate the best answers from the community:
https://discuss.streamlit.io/t/streamlit-deployment-guide-wi...
Depending on what you are trying to do, I suspect you're looking for using Apache2 or nginx as a proxy:
https://discuss.streamlit.io/t/configuring-apache-2-4-for-pr...
If that's what you're taking away, we need to improve our marketing copy!
The point of Streamlit is to have a nimble way to create applications, where auto-refresh/hot-reload is part of the developer experience. But the goal of the overall project is to make interactive data apps available to the broad public, not just people who have front-end experience or a front-end developer working on their team.
You're absolutely right that Streamlit isn't a Jupyter replacement (we're not trying to be!), in the same way that Spyder isn't a "replacement" for the JetBrains set of IDEs. Maybe Streamlit will one day move to multiple language support, but for now, we're trying to be the best Python library we can be for creating web apps.
As far as GPU-support goes, as mentioned above, Streamlit "supports" GPU in as much as Python does. It's important to separate out front-end/UI from backend. If something is supported with GPU as a backend, "data science" (however defined) functionality, Streamlit supports that in the same way a React app calling a GPU API endpoint or other workflow is "GPU-enabled"
For example, it feels like the author would argue that it's "worth" seeing the Grand Canyon, but not worth seeing Space. But the idea of being outside of the Earth's atmosphere, or better yet being able to see the entirety of Earth from the Moon would change my life in ways I'm sure I can't even imagine.
It's common to pay for internet and electricity? I've heard of covering cell phones and things for people who legitimately are on the phone (sales/biz dev), but not down to electricity bills and rent.
Whether that's making a few sentence Slack messages to your team company when you hit milestones, sending out quality email summaries along with a presentation you made, you need to be really deliberate.