ManuelDeLeon
commented
6 years ago There's a whole lot of nastiness involved in making Tracker work out of the box with React render method. Meteor devs would have to pay that tax for the privilege of not using an autorun or observer. Not to mention I'd have to maintain a separate babel plugin package.
On Oct 7, 2017 9:27 AM, "Antonin Adert" notifications@github.com wrote:
I thought about your proposal to remove tracker from ViewModel for performance. Why not just putting it as a separate plugin for Viewmodel so we just upgrade VM version but can still support Tracker inside VM if we install the plugin?
Maybe I am naïve to technical considerations so tell me if this is feasible?
This would avoid backward compatibility breaks and would allow a nicer syntax for all meteor users not concerned about performance that much.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ManuelDeLeon/viewmodel-react/issues/34, or mute the thread https://github.com/notifications/unsubscribe-auth/AED31iw6VH78Sc1giQ78YfAr9ERUe6_Uks5sp5hJgaJpZM4PxYuN .
I thought about your proposal to remove tracker from ViewModel for performance. Why not just putting it as a separate plugin for Viewmodel so we just upgrade VM version but can still support Tracker inside VM if we install the plugin?
Maybe I am naïve to technical considerations so tell me if this is feasible?
This would avoid backward compatibility breaks and would allow a nicer syntax for all meteor users not concerned about performance that much.