Comment by kridsdale1

3 months ago

I wanted to comment on that persistent data point that on Apple platforms, you’ll have NSUserDefaults (objc) and UserDefaults.myVar (Swift). It works just like the author wishes. Other than single thread access, there’s no major problems with it. If you design your program in a way that it falls apart if the use of it is not regulated, that’s on you.

2 comments

kridsdale1

Reply
9rx  3 months ago

> on Apple platforms, you’ll have NSUserDefaults (objc) and UserDefaults.myVar (Swift). It works just like the author wishes.

You could write something similar to NSUserDefaults in any language for any computing environment, but that's not what the author is talking about. He is talking about the same basic concept, yes, but where it exists within in the language itself, not something implemented on top.

c-smile  3 months ago

NSUserDefaults is a key-value storage. Same as localStorage in browsers/js.

On other side persistence in QuickJS is more than that. Essentially it is a NoSQL DB integrated into the language and its runtime. For example you can write

   let uname = root.users[2].firstName;

to access the data using pure language constructs. While with NSUserDefaults you will need to call DB's facade methods like objectForKey("some") and so on.

And also, in QuickJS, Storage is not reading whole DB in memory but fetches/unloads data on demand transparently for the user. You can think about content of DB as about genuine language data structure with root at storage.root