A re-render in React is not as heavy as you'd think it is. It's painting the DOM that takes resources, and people conflate the two. But if your whole component re-renders because of a change in context, yet nothing on the page changed, you will likely not notice the render even on low-end devices.
I still think Zustand is the simplest state management, while staying efficient. It's similar to the old Svelte stores. But I have used many state management tools and the re-renders were not the problem when it came to speed.
A "compiler" to solve the issues the library created, awesome. It doesn't solve many re-renders tho, as React re-render full components, not only the HTML/Text Nodes that changed.
I used mercurial in anger for about 9 months or something, with a gitlab fork too. when git goes wrong there's forums, blogs, books and manuals. When hg does it's a python stack trace, good luck.
The core tenant of this I'd rather push is project based learning. Otherwise it sounds a bit too much like the point of education is to do a job and earn money.
Also touched on is failure, you can't learn a business with real money without failing to make any money, and failure is important and just as much of a passing grade in a project context IMO, depending on grasping the failure.
I don't know the ins-and outs of how audioContext is implemented but it's got a lot in there to be very clever and dynamic, playing a notification chime seems like that feels like drawing an svg with D3 instead of img href *.svg. I wonder if there's a serviceWorker hook that could register simple repeatable stuff like notification handlers much lower down on a more efficient API.
Why does the UK have such trouble with smart meters? Everyone here, Norway, has one because they are required by the government. I haven't heard of any significant troubles and we've had them for years.
Quasi-government incompetence, mostly, though caused by government cowardace: they more or less just shouted "smart meters, do it!" at the energy industry and let them try to sort it out amongst themselves, which means they had several false starts of crap impementations (the first generation didn't think to allow them to be transferrable between providers! The issues in the North are basically because they decided to go for a low-power mesh network, which is a plan that has basically never worked), as well as the fact that the government hasn't made it a requirement for homeowners, but has made it a requirement for energy companies, so they basically just beg the current holdouts (who have little reason to want one) to let them install one.
Octopus have started doing things like connecting properties in the north to cellular type meters (not supposed to) or using Octopus Mini hubs (connects smart meters using WiFi) as a way of trying to solve the problems
I think the new memo compiler address' this in the most complicated way possible.