Found 432 bookmarks
Newest
Designing for Performance by Lara Callender Hogan
Designing for Performance by Lara Callender Hogan
This practical introduction to web performance helps you approach projects with page speed in mind, showing you how to test and benchmark design choices against page speed.
·designingforperformance.com·
Designing for Performance by Lara Callender Hogan
Developer Initiates I/O Operation. You Won't Believe What Happens Next.
Developer Initiates I/O Operation. You Won't Believe What Happens Next.
As Node.js developers, we are extremely spoiled. The level of abstraction provided to us by JavaScript allows us to focus on creating interesting applications instead of wrestling with low level system concepts such as threads and synchronization. But, whether we like to think about it or not, our JavaScript code sits on top of a lot of low level code, mostly written in C/C++, as shown in the following figure. This article will trace a simple JavaScript function call as it traverses various layers of this figure. A basic understanding of the event loop is assumed. If you need an introduction or refresher, check out this guide.
·cjihrig.com·
Developer Initiates I/O Operation. You Won't Believe What Happens Next.
Don't attach tooltips to document.body | Atif Afzal
Don't attach tooltips to document.body | Atif Afzal
Don’t attach tooltips to document.body TL;DR Instead of attaching tooltips directly to document.body, attach them to a predefined div in document.body. BAD %3Cbody%3E -- temporary div, vanishes when tooltips vanishes --> %3Cdiv%3Emy tooltip%3C/div%3E %3Cbody%3E GOOD %3Cbody%3E -- this div stays forever, just for attaching tooltips --> %3Cdiv%20id=%22tooltips-container%22%3E -- temporary div, vanishes when tooltips vanishes --> %3Cdiv%3Emy tooltip%3C/div%3E %3C/div%3E %3Cbody%3E Introduction Tooltips in our app were taking >80ms. And during this time, the main thread was blocked, you couldn’t interact with anything.
·atfzl.com·
Don't attach tooltips to document.body | Atif Afzal