Here's a tip video on using (at)tracked for event driven reactive data in Ember. 📹 www.youtube.com/watch?v=PZLL...#EmberJS#JavaScript
YouTube video by Ilya Radchenko
I am biased, but I think github.com/emberjs/rfcs... is pretty good in the context of an open source project. The issue was controversial in the ecosystem, and this (along with other writing linked from it) broke a years-long stalemate, and it shipped.
Rendered RFC Summary Adopt <template> tags as a format for making component templates first-class participants in JavaScript and TypeScript with strict mode template semantics. In support of ...
new RFC: recommend arrows instead of `@actiongithub.com/emberjs/r...
Propose Recommending arrow functions instead of the @action decorator. Rendered Summary This pull request is proposing a new RFC. To succeed, it will need to pass into the Exploring Stage), follow...
i hope their hiring manager just put "angular" not knowing the chasm of difference between 1 and 2 but either way its still like building something in emberjs in 2024
✨ ember-source 5.10.2 just released with some very important bug fixes ✨ github.com/emberjs/embe... 🎉
CHANGELOG #20726 [BUGFIX] Fix test waiters by removing unintentional duplication from ember-testing bundle #20715 [BUGFIX] Don't publish empty modules
DAY-UM Congrats on this release of WarpDrive -- this is such an inspiring introduction to release notes! I'm feeling excited, relaxed, and eager to see what is happening here. 🎉 This. Release. is. Huge! github.com/emberjs/d...
The first of my two #lambdaconf2024www.youtube.com/watch?v=0Pyy...#Rust#EmberJS ecosystems will recognize a lot of themes and theses here!
The Cutting Edge Of Versioning by Chris Krycho at #LambdaConf2024. Get your ticket for #LambdaConf2025 here: https://www.eventbrite.com/e/lambdaconf-2025-tickets-903567092497 Versioning sits at the intersection of contract and communications: what our languages and tools can enforce, and what we want to tell the people using our software. Semantic Versioning is one answer to this: a sociotechnical contract which lets us define breaking changes. Because it is social as well as technical, though, it is ambiguous. Members of the Rust and TypeScript communities offer one kind of answer to this challenge: specification and tooling. Elm has offered another: baking it into a language-aware package manager. Unison lets evolution and versioning coexist. One group of researchers even baked type evolution into a functional programming language. Other languages and ecosystems have just thrown up their hands in the face of the inevitable edge cases and failure modes. We can do better! How can new languages include versioning semantics in their design constraints? What tooling should we build for existing ecosystems? Above all, what should you do in your own projects?
