Explain the architecture of Ember Data and what problems it solves and how.
-
-
Replying to @tarasm @oligriffiths and
I can believe we could be doing this better and it would help. I have a talk in a few weeks. Why should I focus on?
1 reply 0 retweets 2 likes -
Replying to @wycats @oligriffiths and
It might be better to train a few embassitors with 3-4 more junior talks that would appeal to JS community and have them apply at every conf
1 reply 0 retweets 4 likes -
I would agree. Need to initiate next wave and give them opportunity to thrive in what is now often considered Senior dev land
2 replies 0 retweets 3 likes -
I think the core needs to answer this question better:"I've invested xx hours in this framework, why should I tackle ember?"
1 reply 0 retweets 1 like -
I.e. What does ember give me that react 16 won't?
1 reply 0 retweets 1 like -
Indeed! 1: - build tools that work out of the box - a built in sophisticated router
3 replies 0 retweets 6 likes -
2: - a focus on avoiding breaking changes (drop in upgrades) - community governance - regular release cadence (w/ LTS if you want it)
2 replies 0 retweets 3 likes -
3: - helps you migrate your app over time to target the latest ecosystem. - built in testing with the same stability story
2 replies 0 retweets 3 likes -
4: - a built in data story that Just Works™ with JSONAPI and can be configured to work with other backends.
1 reply 0 retweets 0 likes
5/5: - add-ons that work with all of the above, & are a first class concern of the framework evolution process. - more that didn't fit
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.