Hi @cbaker6 - thanks for your reply.
My comment on ‘reactivity’ isn’t related to LiveQuery. I’m aware that LiveQuery (a great feature, btw!) exists and I’m using it. But that’s not what I’m referring to.
When we say reactivity in terms of Vue or React, we’re referring to binding the data object to the UI, such that when the data changes, the UI automatically updates to reflect the current state of the object. In Vue’s case this involves Vue’s internals binding setting setters/getters (Vue 2) or Proxys (Vue 3) which trigger updates to the UI surgically as needed, only where a value has actually changed (so they don’t need to re-render the entire component.
The problem - and its a big problem for Parse, IMHO, given the popularity of React and Vue (and friends) - is that the underlying state of the data in Parse Object is only exposed by EITHER a frozen object (object.attributes) or through get(path) - neither of which is or can be made ‘reactive’.
I am a part of the other thread you mentioned. The concept is to create a POJO representation of the current state of the Parse object and keep it in sync - either in real-time as sets/gets occur, or per @dblythy on read/save only … but it’s not so easy to keep the data in sync (firstly) and not so easy to provide a useful representation of the data given relations like Pointers, Relations, ACLs etc. as any of these fields will not be reactive even if the primary object you’ve mounted is.
If the Parse community would like to engage in discussion on how to best make reactivity a possibility in Parse, I would happily participate. I personally feel it’s a major disadvantage for the platform that limits its usefulness in modern UIs. All the cool kids are using React and Vue (and friends) lately … and for a very good reason. They allow us to build powerful applications reliability and quickly. It’s almost a perfect fit for Parse, as the visions are not so different … but without first-class reactivity of the data, that value proposition is diminished.
All my own opinions. Please don’t roast me