Five Frontend Things Friday #16

Here are five things in the Frontend Engineering world, that I found interesting…

  1. Modern Front-End Frameworks should be less of a “frame” and more of a “work” - Avichay Eyal, on his Medium blog, “By sticking to “use the platform” approach and use native APIs, it will do good for us all in the long run.” A good read of the current state of the Web Platform and JavaScript in browsers, how we got here, and what we should do about it.

  2. The Cost Of JavaScript - Addy Osmani, Eng. Manager at Google working with Chrome & DevRel, on the Chrome Dev Channel Medium blog, “As we build sites more heavily reliant on JavaScript, we sometimes pay for what we send down in ways that we can’t always easily see. In this post, I’ll cover why a little discipline can help if you’d like your site to load & be interactive quickly on mobile devices.”

  3. Using CSS Grid: Supporting Browsers Without Grid - Rachel Andrew on the Smashing Magazine website, “When using any new CSS, the question of browser support has to be addressed. This is even more of a consideration when new CSS is used for layout as with Flexbox and CSS Grid, rather than things we might consider an enhancement.”

  4. Advocating for Accessible UI Design - Lara Schenck on the CSS Tricks blog, “Accessibility is a hot topic these days, and the older we web-makers get, the hotter it’s going to become! That might be a snarky outlook, but what I’m trying to say is that it’s about time we start designing the web for everyone because the web was meant to be for everyone, and less and less are we able to predict where, when, and how our work will be consumed.”

  5. Must Watch JavaScript - A useful list of must-watch talks about JavaScript

Keep Rising,

Kevin B. Ridgway

Like this list? Want to get it in your inbox?
Sign up for newsletter!