Yeah I'm excited to fix it as long as people working on alternatives avoid disparaging ED (and its users). I think @dgeb and Orbit have been shining examples on this front.
-
-
Hey, thanks! I think there are a lot of good ideas to share in this space. And this next year we’ll be able to collaborate on shared primitives rather than focusing on separate silos.
1 reply 0 retweets 1 like -
I think there is a lot that can be say already without waiting for the shared primitives. Talking about the current state would help others get involve or to actively debate alternatives.
1 reply 0 retweets 1 like -
Yeah, I completely agree. And we’re going to try to expand and improve our messaging on this front.
1 reply 0 retweets 1 like -
When you say “we” who are you referring to?
1 reply 0 retweets 0 likes -
Both the core + data teams. The central messaging is that, while ED will remain the default, it is not required (and other solutions are not discouraged). And the data team is focusing on making ED more modular and lightweight, with stronger primitives.
3 replies 0 retweets 0 likes -
I’m glad to hear it. ED is awesome, but the docs make assumptions that you will be using it. I put some thoughts down here https://gist.github.com/oligriffiths/cff30253e2c2d7534494e6f11679fc7d … lmk what you think.
2 replies 0 retweets 5 likes -
Replying to @oligriffiths @mamadero and
Thanks Oli. I think that’s a reasonable take and I largely agree with your points (although there are also pros to bundling a simpler default ED without adapters / serializers). I’ll definitely share this with the team!
1 reply 0 retweets 1 like -
Great. I think some form of simplified data persistence might be a good default. Ember already has model hooks but it’s not clear the boundaries between that and ED.
1 reply 0 retweets 2 likes -
Replying to @oligriffiths @mamadero and
I agree that that there is some implicit behavior that should be made more explicit. Muddy boundaries don’t help the messaging.
2 replies 0 retweets 1 like
I think that as we move towards running model hooks every time, at least a simple identity map will be needed to avoid footguns. But I think we can keep the mental model reduced to an identity map (and one you could remove if you want).
-
-
Are you thinking something like and @ember/data-core to match @ember/core
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Seems reasonable to me.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.