- Lots of invisible behind the scenes model work. Built classes for timelines, users, posts, etc.
- Posts for the main timelines now persist to a cache file loaded at launch. Reduces latency of launch, but will need more work to stitch updates with stored data.
- Doing speedy work with a unique-object set is pretty useful for an app that has lots of chronological timelines. ES6 has a nice Set class and even a WeakSet class. /Yea!/ Who knew? But they don’t have any sort of built in mechanism for comparing or hashing objects. /Booo!/ Lots of solid solutions on npm. Lots of lulz solutions on SO.
- Timeline now has a few hundred posts. Scrolling still very nice. Window resizing… well… still great on non-retina… but on retina resizing the really large images is pretty ugly. To be expected. Should I dynamically populate just portions? Dunno. I’ll experiment later.
What is this: these are random snippets from my dev journal working on a simple client app for fun. This is a non-serious side project, progresses very slowly, and will probably never see the light of day. The images may not perfectly correspond to the journal entry. In most cases I’ve added them later based on the relative time of git checkins.