In the context of LLMs memory can often mean a broadly defined, application-specific ability to detect, retain and re-use bits of useful context along the journey. In contrast to Persistence which is more like a DB with a schema and clear expectations, reliability, etc.
Totally agree. Persistence is a huge part of what we usually mean by state. Nothing stops this from plugging into a real database when needed. But also, nothing stops us from rethinking what a database even is, especially in a world where LLMs have growing context windows and can carry more state internally. Maybe persistence doesn’t always have to mean "write to disk."
good question. I think it'll be self-reinforcing, since the context keeps growing with everything the software has done for you, along with every interaction you’ve ever had with it.
honestly, kind of both. it started as a curiosity. I just wanted to see if it could even work. but after playing with it, I think there’s something deeper.
the most interesting part to me is the idea of apps that self-customize without being told to. they adapt based on how you use them and what you enter, not from settings or configuration. stuff that changes itself in real time, just by being used. we wouldn't build that kind of software today because it's too weird or specific. but with this, it just happens.
still super early and pretty rough, but it feels like a door opened a crack.
Speaking of the AirPods becoming actual hearing aides - how will we reconcile the fact that it is not socially acceptable to wear AirPods when speaking with someone?
Even if you get to explain ‘oh my AirPods are functioning as a hearing aide’ you likely won’t be able to explain that to other people noticing the conversation and thinking to themselves ‘oh that’s douchey, not taking our your AirPods when talking to someone’.
I just really wonder if this will be able to make wearing AirPods while talking to other people socially acceptable because the current presumption is likely that they are not behaving nicely.
In 1998 Assembly programmers who typically participated in Demo competitions did a series of size coding challenges. The first one was a Snake game (Nibbles), all in a DOS environment. The winning entry was 48 bytes long.
There were also some creative attempts that took less than 48 bytes and got disqualified. One of those encode the entire game in a series of empty folders using the folder names.
Edit: the original Hugo size coding competitions were created by Claus-Dieter Volko (Alias: Adok).