GitHub: https://github.com/widgetti/wanderlust App: https://huggingface.co/spaces/solara-dev/wanderlust X: https://twitter.com/maartenbreddels/status/17223244907077020... Solara: https://github.com/widgetti/solara/
GitHub: https://github.com/widgetti/wanderlust App: https://huggingface.co/spaces/solara-dev/wanderlust X: https://twitter.com/maartenbreddels/status/17223244907077020... Solara: https://github.com/widgetti/solara/
I want my ai to have as little financial incentive for itself and only maximize my needs. I'd pay for THAT.
In the end, you'll end up with Booking.com with extra steps:
"Perfect, ugh123! I've got just the hotel for you! It's the Marriott Grand Paradise, our top partner hotel. It is only 45 miles away from the specific address you requested and just barely $150 over budget per night, but they have a 4.9 rating, and with their Top Partner status, you earn 10 BookiePoints by booking there. Hurry, 33 people have booked a room there in the last hour! Do you confirm? Whoops, one more booking just now, only one room left! Do you want to save yours now?"
because it's not like human travel agents don't exist today, just like human drivers exist today. Does having an AI book the tickets for you meaningfully change the things for you, the customer?
Of course it does. You don't think replacing humans in the full service travel industry wouldn't drive down costs and upgrade capabilities and experience could be a thing?
I am finding myself reaching for GPT4 more often to spin up POC apps.
You could fine-tune a coding assistant on your library and good quality example apps with documentation ... and that might take the ease of churning out new demos and apps to the next level?
I ask it to write it in small chuncks but in the same context. I sometimes have to remind it to refer back to decisions we made earlier.
* Solara will not continuously re-execute your script as Streamlit does.
* Solara will re-execute components instead, only what needs to. * State in Solara is separate from the UI components, unlike streamlit, where they are strongly linked.
* State can be on the application level (global) for simplicity or on the component level (local) for creating reusable components.
* Solara should not block the render loop. Long-running functions should be executed in a thread using use_thread.