I see you already open-sourced dust. I love this one too.
So is it dust like "des grains de poussière qu'on assemble ?" ;-)
Anyway, you chose the most direct "Data flow Programming" approach. It is neat and works at a flexible level.
However, one of the amazing things about ChatGTP is its ability to remember and respond to incremental "conversational" prompts in a smooth way.
How to integrate this kind of manual feedback-like "flow" within that other more rigid automatic "dataflow" of dust is something to think about, I guess.
It is not just "time for AI-native products!" [1], it is now time for "AI-prompts-native products", and yours are more like platforms than products. This is what I like about them.
A lot of coming pseudo-apps are going to be really just simple prompts in disguise [2]. So open platforms are the way to go.
Comments
I see you already open-sourced dust. I love this one too.
So is it dust like "des grains de poussière qu'on assemble ?" ;-)
Anyway, you chose the most direct "Data flow Programming" approach. It is neat and works at a flexible level.
However, one of the amazing things about ChatGTP is its ability to remember and respond to incremental "conversational" prompts in a smooth way.
How to integrate this kind of manual feedback-like "flow" within that other more rigid automatic "dataflow" of dust is something to think about, I guess.
It is not just "time for AI-native products!" [1], it is now time for "AI-prompts-native products", and yours are more like platforms than products. This is what I like about them.
A lot of coming pseudo-apps are going to be really just simple prompts in disguise [2]. So open platforms are the way to go.
[1] https://aigrant.org/
[2] Example from HN today : https://news.ycombinator.com/item?id=33975805
Dust XP1 runs on a Dust app. You just need a "history" input parameter that gets injected at the right place. Does that make sense?
It does.