NativeScript iOS Daily: Rethinking Per-Isolate State
A single runtime commit introduces typed per-isolate state storage on Caches, replacing ad hoc members and shared maps with a safer, teardown-aware pattern first adopted by console-dot-time.
Duration: PT1M56S
Episode overview
This episode is a short developer briefing from NativeScript iOS Daily.
It explains recent repository work in plain language.
- Show: NativeScript iOS Daily
- Published: 2026-08-19T13:15:03Z
- Audio duration: PT1M56S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's August 19th, 2026, and this is NativeScript iOS Daily.
Today's activity is small but structural: one commit that changes how the runtime manages per-isolate state, and it's worth understanding why.
Eduardo Speroni's commit, short SHA a-b-e-seven-f-f-e, adds what's called "State For" on Caches — a way for a subsystem to get its own per-isolate storage, declared in its own source file, instead of bolting a new member onto the shared Caches header or relying on a process-wide map keyed by the isolate pointer.…
The new model is deliberately modeled on the Android runtime's Runtime State — state is created on first use, destroyed alongside Caches under the teardown lock while the isolate is still alive, and made unreachable once teardown begins. That's a much clearer lifecycle contract for anyone building a subsystem that…
The first real user of this pattern is console-dot-time. Its label map, previously living inside the Caches header, now migrates out to use the new typed storage. It's a small functional change on the surface, but it's really a proof of concept for the broader pattern — a template other subsystems can follow instead…
What to remember: if you're adding…