Replies: 3 comments
-
The next gen executable strategy was not without merit - especially around how it batched. However it created other problems
|
Beta Was this translation helpful? Give feedback.
-
Next gen was pretty much a playground of ideas, but they were never viable enough for a general purpose replacement of the current engine. Additionally to points by @bbakerman I would highlight the immutable result tree ( I agree @btserket that the batched execution is very nice: our goal is still to provide such a batched execution algorithm without dataloader, but we have not really found the right overall design to offer that. |
Beta Was this translation helpful? Give feedback.
-
Thank you @bbakerman and @andimarek for the explanation! Much appreciated. |
Beta Was this translation helpful? Give feedback.
-
I've noticed the nextgen engine is gone from the master. I can imagine it wasn't widely used, but it offered an infinitely easier alternative to batching (as compared to DataLoader), worked just fine in many use cases, and... well... was supposed to be the next generation.
Maybe @dondonz or @bbakerman can shed some light on the decision.
Beta Was this translation helpful? Give feedback.
All reactions