Skip to content

Comment on Spritely Goblins v0.13.0: Object persistence and easier IOparent

Comments

You'd still need a mechanism for persisting separately, or you'd end up with a broken image/"data layer" due to post-crash persists.

It's common to do something similar by writing most of an application as functions over a database and static files, and using scaffolding tools to reinitialise the database when things break.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.