Alright, this might be a bit out there, but hear me out—I think you'll appreciate where I'm coming from: what if variables could be made persistent?
I know, traditionally, variables are tied to the application lifecycle - and persistence is not built-in by design. When an app reloads, variables reset to their default values, which makes sense. - But what if we had the option to make specific variables persistent, even after a reload? A variable could be globally persistent, meaning any change by one user would update it for everyone, in real-time.
Now, let’s take it a step further. What if persistence wasn’t used shared across all users, but optionally per user? Imagine a scenario where a user updates a variable, and they continue seeing that value next time they use the app—while other users would still see their own defaults or updated values.
At this point, you might be thinking, “Isn’t that just a database?” And yes, in some ways, it is. But this approach could be far more accessible, removing much of the complexity of database design. Unlike localStorage, which is isolated per user and has limitations, this would allow seamless sharing of state across sessions and even users.
As a bonus 
, imagine the editor view providing an overview all variables and their values per user. That could be helpful for insights, debugging, fine-tuning, or collaborative applications.
I'm curipus to what y'all think. Should variables stay the way they are, or would you be open to a more persistent approach?
I would love to hear your opinion! 
I have to admit, it's a bit out there, but as with many abstract ideas, it's often only after they become feasible that people start using them in unexpected ways.