Some studies say as much as 80–90% of page load time happens on the client side. If we build pages with an eye towards more efficient browser rendering, the impact on overall performance can be dramatic. The most valuable parts of Scott's article are the tools. Humans can't quantify what we perceive in milliseconds, and we don’t think in terms of bytes. Using automated utilities to measure these units accurately can help us get a more accurate picture of real world performance, and catch changes that make things better or worse. These subtle improvements make projects more efficient and delightful for users. As our requirements with responsive web design become more complex, prioritizing performance becomes even more important.
Sometimes it can be tough to figure out what actually occurs in the browser when various CSS properties are used. Thankfully, Paul Lewis has written a tool that can decipher what CSS properties trigger layout, paint, or composite actions in the browser. By understanding these better we can make real improvements to Front-end performance.
Some say that Vim is the most extensible text editor available, but it can be intimidating to get up to speed with this application. Among other things, it requires UNIX experience that's more commonly associated with Back-end Developers and SysAdmins than Front-End devs. In his article, Ben Frain shares great tips on how to get comfortable with Vim as your editor of choice.
Complex layouts can be difficult, given the limited set of CSS properties most browsers support. Thankfully, the Flexbox layout model is beginning to get enough traction to be a viable option for some projects. In this article, Zoe Gillenwater shares an example of a complex “pinned” layout. She shows off two approaches: the display: table property, and the more elegant Flexbox solution that's catching on.
What Happened Recently
- IE11 mobile now supports
-webkitprefixes — via @stopsatgreen
- The Responsive Images Community Group (RICG) are facing a name change as work shifts from the successful
<picture>implementation to other responsive solutions (element queries). —@respimg
- Marcos Caceres made a proposal to add a "
<source>generator" for Firefox Developer Tools — @marcosc
- CSS outlines in Firefox expand to cover overflowing text —@simevidas
- A call was made for companies to fund Ruby Sass performance improvements. —@nex3
Craving more? Subscribe to our Flipboard mag for daily updates or sign up for our newsletter below.