;WE COULD NOT FIT THE NUMBER INTO THE BUFFER DESPITE OUR VALIENT
;EFFORTS WE MUST POP ALL THE CHARACTERS BACK OFF THE STACK AND
;POP OFF THE BEGINNING BUFFER PRINT LOCATION AND INPUT A "%" SIGN THERE
;CONSTANTS FOR THE RANDOM NUMBER GENERATOR FOLLOW
;DO NOT CHANGE THESE WITHOUT CONSULTING KNUTH VOL 2
;CHAPTER 3 FIRST
Edit: GW-BASIC, not QBASIC (https://github.com/microsoft/GW-BASIC)If I might ask, how was your experience working with the TickTick API? I've been waffling on whether my frustration with some of the pain points I have with it (e.g. no way to hide recurring daily tasks that you've already completed today but aren't actionable for tomorrow from cluttering the "tomorrow" heading in every smart list) justify building my own dashboards for it.
Allows the clients to remain connected and be none the wiser that there was an update at all.
For larger updates we just do hard restarts when in-memory data structures or supervision tree are changed.
The article just says they pushed through and “put it aside”, but that has never seemed to quite work for me. I can push through once or twice, not enough to build a daily habit/obsession like I want.
Anyone have any tips that worked for getting over this hurdle?
Deleted Comment
I’m not very experienced with BEAM, but could its features be delivered with a framework on top of a different stack? I know Akka is popular.
I think there's something close - https://caramel.run/manual/