developer.chrome.com VS immutable-js

Keep up with all the latest landings in CSS and HTML right here on developer.chrome.com and check out the I/O videos for more web landings.

Hola developers and learners 👋👋!! We are going to start a new blog series on Chrome Developer Tools. As a web developer, you know that having the right tools can make all the difference when it comes to building high-quality, efficient websites. But fear not! Chrome DevTools Elements section is here to save the day, like a superhero swooping in to solve all your web development woes 🦹.

developer.chrome.com https://developer.chrome.com › docs Lighthouse overview - Chrome Developers

Read the documentation https://developer.chrome.com/docs/extensions/. Build an MV3 for each API. File issues https://github.com/GoogleChrome/developer.chrome.com when you find inaccurate content.

where that is not what is really going on, because Chrome and Chromium browsers do not support capturing system audio. At best the audio captured is the tab audio. Try to capture the system audio produced by window.speechSynthesis.speak() and see what happens, see https://github.com/GoogleChrome/developer.chrome.com/issues/3957 https://github.com/GoogleChrome/developer.chrome.com/pull/3947#issuecomment-1274250421

developer.chrome.com

Keep in mind that getDisplayMedia() does not capture all audio output to speaker or headphones, e.g., does not capture window.speechSynthesis.speak() output, which is not output via the Tab audio, see https://github.com/GoogleChrome/developer.chrome.com/issues/3957.

Yep, they just updated when CWS stops accepting MV2 updates to January 2024: https://github.com/GoogleChrome/developer.chrome.com/pull/38...

Visit any website on https://developer.chrome.com or https://docs.microsoft.com

immutable for JavaScript.

Check out Object.freeze. There's also Immutable.js for working with immutable data.

Use immutability to manage state updates When updating state in your React application, it's important to ensure that you are not mutating the original state object. Instead, you should create a new copy of the state object with the updated values. Immutability makes it easier to manage state updates and ensures that the updates are performed in a predictable and safe manner. Libraries like Immutable.js provide a set of functions that simplify working with immutable data in React applications.

We're wanting to get rid of immutable so I'm trying to replicate what it is about the Record functionality and types that allow this dynamic property access to work. After pulling my hair out looking through the [email protected] type definitions and the actual code, to me it looks like the types are just kind of lying about what's going on ... and it's just working. Does anyone have any ideas how I can replicate this dynamic property access with strong typings?

The Immutable.js README has a much more complete description of immutability and why you might want to use the library. Also worth mentioning that Immer is an alternative which is a bit easier to get started with.

Examples: immutable-js Immer

I can't speak to C# and Java, but the suggestion in this post: ImmutableJS already uses Persistent data structures. (It's the second sentence of their introduction)

Avoiding mutation is just never modifiyng an object, ever. There are tons of implementations of this pattern, notably immutable.js (https://immutable-js.com/), Redux is also an example of this philosophy.

JavaScript is most programers' first introduction to map, filter, and reduce. Easy lambdas made those higher-order functions a staple of a lot of JS code.

Meanwhile, immutable.js[0] is at 10 million downloads per week and rising.

I would add that it's not just the ease of use of lambdas, but the fact that in JavaScript functions really are first class citizens. Most of the other widely used languages that people start on have lambda functions added in as a bit of a hack and only treat some functions as real values.

[0] https://www.npmjs.com/package/immutable