In How Autotracking Works, Chris discusses how autotracking fulfils the reactivity design principles exploring how it's implemented and why. In the blog, we go through memoization, referential equality, revisions, tags, and how they all work together to provide autotracking for Ember.
Autotracking revolves around a single number, the global revision number. This number keeps track of the version of state that the application was in. However, we don't want our memoized functions to rerun whenever the state changes, because it could have changed for a completely unrelated state. We only want to rerun whenever the tracked state within the function has changed. For that, we need tags which represent state within the application so our function only reruns when it should and unrelated changes will not affect it.
Maybe you haven't noticed, but the primary website for Ember has been redesigned and it is now live! The redesign brings a fresh new look to the main piece of real estate for Ember on the internet and features a clean and modern look that all of us in the community can be proud of.
This redesign has been a long time in the making and has involved a lot of work from the people from the Ember Core teams and the Ember community. Big shout outs to everyone involved in the effort, especially Mel Sumner (@MelSumner) and Chris Manson (@mansona)! 🎉🎉🎉 It's super exciting to see this modern vision of the website come to life.
If you are enjoying the new website and would like to help with making all the Ember web properties have a consistent design, please let the Ember Learning Team know in the #dev-ember-learning channel on the Discord chat.
Here's another friendly reminder that it’s that time of year again 😀, the 6th annual official 2020 Ember Community Survey is here! Once again we would love your help to learn about who is in the Ember community and how they work with the framework.
Last year over 1200 people participated in the survey. All that participation and your participation over the years has resulted in enough input to make the process more efficient. This year the survey has been considerably slimmed down from previous years! So it should be easier than ever to make a contribution to our community by filling out the survey – let’s keep that participation going! 🎉
This year we’d also like to emphasize that contributions from non-Ember users are valuable as well. So if you have co-workers or friends who you think might be interested in filling out the survey, please share it with them.
Submissions will be accepted until March 8th, but there’s no need to wait! Go ahead and fill out the survey here now. 🔥🔥🔥
We look forward to your participation! If you have any immediate questions, feel free to email the survey team via firstname.lastname@example.org, or ping them in #dev-ember-learning on the Discord chat.
But please, don't forget to help us spread the word by sharing the survey landing page on your social network feeds, at meetups and around your office and other communities.
It's not too long until Ember 3.17 is out and until you can upgrade your favourite Ember app to the latest version of the framework. If you want to have an extra head start, you can even try out some of the 3.17 Ember experience today!
But why is beta testing important in the first place? A distributed community project such as Ember not only lives from the code contributions of developers from all over the world, but also from their feedback about current releases. Early adopters and ambitious testers of releases in the beta and canary channels can provide the insight that is necessary to cut the upcoming release of Ember efficiently: with the best possible developer experience for the entire Ember community in mind.