From 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 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.
It's realistic. ST isn't about building huge projects. It's basically an interactive plot tool which is easier to use and more flexible than existing python solutions. 99% of streamlit code is useless in a month, and that's fine.
It's also great for internal debug tools, where I want to give people an easy "put some data here and get back relevant info from various different systems / logs".
Dave 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.