yeah, I think this can be built with caching primitives, where your app-level code doesn't need to concern itself with this but transparently receive this functionality

it's one of the reasons why I built #[2], because this is a problem that needs to be addressed, and having a more "definite" source which you can ask for these type of data might be useful

but yeah, apps need to have this stuff abstracted away; we can't expect all apps to reinvent these things

Reply to this note

Please Login to reply.

Discussion

No replies yet.