Do i need to specify J-Dtrace as an argument to JVM arguments when starting a local api server via intellji? It's mentioned as an argument on the command line, but not explicitly in the instructions for intelliji. If i run it with it, then i get an immediate exception (no further info). If i run it without, i get "Starting nRepl server". Which would seem to be correct, but it then times out with "No nREPL ack recieved". Which im currently trying to understand. maybe clj is out of date, if i run it from the command line it just hangs (no visual output). oh, the command line finally finished. took way longer then expected.

Regarding this: http://book.fulcrologic.com/#_why_not_have_components_just_grab_their_data_sideband i'm not sure what the question > what is the data model? implies. Are we asking what that query semantics of fetching the data would be if components pulled data directly from a global client db? > How do you interact with remotes to fill your data needs? What do we mean by "remotes"? hmmm ok, looks like tony has a whole article on this: https://fulcro.fulcrologic.com/networking/2017/12/26/remotes-as-an-abstraction.html In the example the remote isn't updating the source (local storage), the article points that out, but i'm assuming if you actually used this abstraction the point would be to update local storage. On terminology, the article says "this demo does not do optimistic updates". I feel like i must be getting confused, i thought an optimistic update in this context would mean updating the UI via the atom which is a ephemeral, which this demo is doing. It's not updating the local storage though.