Comment by jncfhnb
1 year ago
State is a function of accumulated past. That does not mean that having some past written down makes you stateful. A stateful thing has to incorporate the ongoing changes.
1 year ago
State is a function of accumulated past. That does not mean that having some past written down makes you stateful. A stateful thing has to incorporate the ongoing changes.
Which is what I described: some successful prompt-replies are fed back into subsequent training runs.
No… that implies the model never has active state and is being replaced with a different, stateless model. This is similar to the difference between
Actor.happy = True
And
Actor = happier(Actor)
Both of your examples are stateful systems from the outside, given a suitable choice of timeframe, the latter one is just how purely functional systems represent state. Theoretically they can simulate each other, and the endpoint you use to access Actor will still reference the latest Actor. The only reason you're calling them different is because you insist on using a specific timeframe to exclude considering one as stateful, and I'm pointing out that that isn't strictly necessary.
1 reply →