Another gem from Paul Irish. This site answers the question “How available are the web platform’s features?”

Powered by data from caniuse.com and StatCounter, this page indicates the percentage of users who have a browser that natively supports various web platform features. Obviously, this doesn’t consider polyfill-ability or other fallback scenarios.

Caniuse data updated September 22, 2016. StatCounter data (global) from August 2016.

What I really like about this site, is that it lists the DOM APIs compatibility.

From Eric Adams writing on his blog:

Promises are very simple once you get your head around them, but there are a few gotchas that can leave you with your head scratching. Here are a few that got me.

Good rundown from Eric, of the gotchas when dealing with promises in the JavaScript promises library Q.

TLDR:

• New Data Type called Maps
• Source Maps
• Tons of smaller improvements

See the entire changelog here.

Each week we will do the hard work of trolling through the blogs, rss feeds, tweets and plus posts to find the latest developments and trends in the world of reponsive web design.

Do you like websites? Do you like websites that are responsive? Subscribe, and learn about responsive design.

weekly e-mail
roundup of css articles,
tutorials, experiments and tools
curated by Zoran Jambor

A nice collection of CSS articles every week.

A once a week email with no spam, no rambling. Just pure awesome links to the best news and articles to hit the interweb during the week.

Not necessarily a frontend specific newsletter per say. But I consider some form of web design to be under the umbrella of frontend engineering, even if it just means “designing” where things are placed on a page in HTML. It matters, and it’s important.

I would say even four years ago, or so, testing visual UI regression wasn’t easy. Most developers probably just gave a quick glance in as many browsers as they could. This is a time-consuming and inefficient way of testing.

There are more tools to help us do visual regression testing automatically, and even integrate with Continuous Integration workflows. (You’re doing builds, and CI, right? You should.) I’ve found a few that look interesting:

• https://github.com/facebook/huxley
• https://github.com/BBC-News/wraith

A take on a very popular FE framework.

Alex Sexton writes, on Smashing Magazine:

A front-end operations engineer would own external performance. They would be critical of new HTTP requests, and they would constantly be measuring file size and page-load time. They wouldn’t necessarily always worry about the number of times that a loop can run in a second — that’s still an application engineer’s job. They own everything past the functionality.
They are the bridge between an application’s intent and an application’s reality.

Yes! Web application frontends are getting so complicated, and so big, specializations like these are needed in companies.

Glad, Alex wrote this. I had been thinking along similar lines that past few months.

Alex MacCaw. author of JavaScript Web Applications, and The Little Book on CoffeeScript, has a new project that I like quite a bit.

From his blog post announcing it:

Monocle is an experiment in creating a friendly and intelligent community around sharing quality content with a focus on technology, startups and frankly anything that appeals to the inquisitive mind.

The articles are sometimes Frontend Engineering specific, and other times just general technology. The interface is clean and useable, and I do like the mobile site for browsing on the go as well.