3 ms·

I highly resonate with this. In fact, I spent over a year buildng it [1]. My thesis is that the calendar will play a significant role in the next OS UI paradig

I highly resonate with this. In fact, I spent over a year buildng it [1]. My thesis is that the calendar will play a significant role in the next OS UI paradigm, replacing the old grid of icons and overlapping windows. Everything will happen around a unified timeline, through which you will launch an app by time-blocking its use, check notifications by looking at the past, forecast battery life or weather by looking at the future, undo/redo actions (or view snapshots/backups) by time traveling, etc. It is shocking how far behind our map of time (e.g., Google Calendar) is compared to our map of space (e.g., Google Maps). Every spatial feature has an obvious temporal equivalent that just isn't implemented. I want to be able to search, save, and review events. I want to schedule an itinerary of events. I want turn-by-turn navigation in time. Of course, solving time is just the beginning. The real magic happens when you combine space and time. For this, we may need to wait for more AR/VR adoption, whose added dimension should make this realization obvious to most and significantly facilitate its implementation. [1] https://chronomize.com/ https://chronomize.com/

samsquire 3y ago
Thanks for your comment. Your mention of combining space and time compels me to share my thoughts about time and space, I am experimenting with a programming technique that models state directly as its primary interface (whereas most programming languages model instructions). Time is inferred by movements between states or interactions with state. I want "turn by turn" navigation of state and time as an implication of that. It's incomplete but here is a point and click programming environment with some numbers and some parsed JSON into a grid. You can move data around between cells and the instructions are logged and the state is captured on each instruction. You "move through" state space. Try moving a value from the top to the bottom or vice versa. https://replit.com/@Chronological/DynamicTables#index.html https://replit.com/@Chronological/DynamicTables#index.html Time travelling is implemented by clicking on instructions (the list items under Program instructions when you have done an action) The goal is to to infer the instructions needed to do the movement, be it pop off the stack or access some inner field in JSON or call a function. It's inspired by spreadsheets and the insight that most programming is logistics.
smeej 3y ago
When you say "spent," does that mean it's in the past and you're not building it anymore? Or are you still actively developing it? I love the idea behind it and would be very interested in using such a service, even if it might require some reimagining from traditional calendar format to make it fun and intuitive to use!
perilunar 3y ago
This was the idea of the Lifestreams project: https://www.cs.yale.edu/homes/freeman/lifestreams.html https://www.cs.yale.edu/homes/freeman/lifestreams.html

samsquire 3y ago

Thanks for your comment. Your mention of combining space and time compels me to share my thoughts about time and space, I am experimenting with a programming technique that models state directly as its primary interface (whereas most programming languages model instructions). Time is inferred by movements between states or interactions with state. I want "turn by turn" navigation of state and time as an implication of that. It's incomplete but here is a point and click programming environment with some numbers and some parsed JSON into a grid. You can move data around between cells and the instructions are logged and the state is captured on each instruction. You "move through" state space. Try moving a value from the top to the bottom or vice versa. https://replit.com/@Chronological/DynamicTables#index.html https://replit.com/@Chronological/DynamicTables#index.html Time travelling is implemented by clicking on instructions (the list items under Program instructions when you have done an action) The goal is to to infer the instructions needed to do the movement, be it pop off the stack or access some inner field in JSON or call a function. It's inspired by spreadsheets and the insight that most programming is logistics.

smeej 3y ago

When you say "spent," does that mean it's in the past and you're not building it anymore? Or are you still actively developing it? I love the idea behind it and would be very interested in using such a service, even if it might require some reimagining from traditional calendar format to make it fun and intuitive to use!

perilunar 3y ago

This was the idea of the Lifestreams project: https://www.cs.yale.edu/homes/freeman/lifestreams.html https://www.cs.yale.edu/homes/freeman/lifestreams.html