Streamlit's $35M Series B
blog.streamlit.io
Streamlit's $35M Series B
1–10 of 41 posts
Re: Streamlit's $35M Series B
#2Re: Streamlit's $35M Series B
#3Looks interesting but has anyone managed to find pricing anywhere?
Re: Streamlit's $35M Series B
#4Dave Cutler of NT fame used to say leaky abstractions are often worse than no abstractions, and early on, it’s often better to go with a lower-level API (for example, what Tensorflow did) because you can add a higher level one later (eg Keras) based on usage and reasonable defaults.
Heavy reliance on strings with logical meaning? Another strong smell.
Streamlit looks very accessible - which is amazing in this space, and I hope they do well - but my prediction is people will be importing “streamlit.v2” within two years.
Re: Streamlit's $35M Series B
#5From a lot of bittersweet experiences, I tend to be very wary of “drastically simple” API products. We often say APIs are forever - so it is so critical to build the right abstraction. When I saw the demo on their page, yes it’s magically (their words) simple, but it also smells strongly of an API that can start leaking as complexity rises. Dave Cutler of NT fame used to say leaky abstractions are often worse than no…
Re: Streamlit's $35M Series B
#6Re: Streamlit's $35M Series B
#7Re: Streamlit's $35M Series B
#8It's nicer than sending someone static results, and it isn't much more effort.
And vastly better than sending a notebook to someone unless you expect them to modify the notebook a lot.
And learning time to make Streamlit useful for a small internal apps is probably ~15 minutes for most people.