Bookmarks (7) clear filters

What Is The Meaning of this!? — Figuring out what this refers to in different contexts is one of the most perennially discussed topics in the JavaScript world, so it’s always good to see a confident developer take on explaining it. Dr. Axel has his take on the matter too.

The Definitive Guide to Streams — One of those posts that will bring you up to speed on a not often discussed area of JavaScript but which is really useful to understand! The Streams API allows you to programmatically read, write, and transform streams of data in a flexible way.

Accessing Hardware Devices on the Web: A Roundup of APIs — Chrome tends to have more unique APIs for hardware access so take care if cross browser compatibility is necessary, but there are a lot of options nonetheless from the Gamepad API or getUserMedia to the Generic Sensor API or Web NFC.

Optimizing Your Pages for the Back/Forward Cache — Firefox and Safari cache the state of entire pages (rather than just the underlying assets) so if you go back or forward, pages can be restored instantly. Chrome is gradually adopting similar features and there are some things you should take into account.

The File System Access API: Simplifying Access to Local Files — You can now read files and save changes directly to those same files directly from JavaScript in the browser. It’s an open standard but not widely implemented yet except in Chrome 86.

Detached Window Memory Leaks — If code causes a popup window to appear but then retains a reference to such a window, a memory leak can occur. This thorough post looks at why, when they occur, and how to solve the problem in your own code.

Are Long JavaScript Tasks Delaying Your 'Time to Interactive'? — Chrome DevTools can now visualize ‘Long Tasks’ (code that causes the main thread to freeze, breaking the user experience) making it easier to debug and optimize away any problems.