Web Development Reading List #130: Opera Mini, Workflow Fragility And Happy Work

About The Author

Anselm is a freelance front-end developer who cares about sustainable front-end experiences and ethical choices in life. He writes the WDRL, and is co-founder … More about Anselm ↬

Email Newsletter

Weekly tips on front-end & UX.
Trusted by 200,000+ folks.

What’s going on in the industry? What new techniques have emerged recently? What insights, tools, tips and tricks is the web design community talking about? Anselm Hannemann is collecting everything that popped up over the last week in his web development reading list so that you don’t miss out on anything. The result is a carefully curated list of articles and resources that are worth taking a closer look at.

What a week! Some people were debating over our npm workflows and security attacks (and sadly not just virtual social engineering ones but real ones in Brussels), we’ve also seen some great new articles that feature the better parts of our community and society. I’m happy to share them with you over this longer Easter-weekend. Cheers!


  • iOS9.3 and OS X 10.11.4 is finally being delivered to users, and with it, Safari 9.1 is out with <picture> element support, CSS Custom Properties, will-change property, unset value and unprefixed filter.
Why Opera Mini Matters
Why Opera Mini matters for designers and developers in the Western world. By Bruce Lawson.


  • “I ran the stats today. Of more than 250 million Opera Mini users, 50% are on Android/iOS and 50% are on feature phones. The second group of people almost certainly have no choice in which browser to use to get a full web experience. That’s 125 million people that the designer-on-stage doesn’t care about.” says Bruce Lawson in his article about why Opera Mini matters for designers and developers in the Western world.
  • In her presentation, Kendra Skeene shares why access by default should be your goal — primarily because accessible code is literally better for everybody.


  • I bet most of you have already heard about it: This week, many of the most popular open source packages broke due to one author pulling all his packages from npm due to a trademark dispute with kik. Finally, npm restored the package without the author’s consent to fix the Internet. This event shows how fragile our development workflow has become these days. If just one person pulls a package, millions are affected. If npm itself pulls the registry, most dev workflows will break. If npm changes the authorship of a module and lets a new author ship another unrelated package under the same old name, things will break. Let’s fix our workflows again and not rely on single points of failure.
  • GSX2JSON is a useful tool to convert Google Spreadsheet to JSON data, available as a simple API.


  • This week has been troublesome for some people. And while some people’s CI builds broke because of missing npm modules, people using the awesome greenkeeper service, experienced a social engineering attack. Someone has created a GitHub account greenkeeperlo-bot that’s very similar to greenkeeperio-bot, copied the avatar and sent around a couple of useless Pull Requests. Gladly it didn’t end up becoming a malicious attack but shows that even experienced developers just trusted it and merged it without reviewing the changes. Be careful and review your code extensively, all the time!


  • The W3C published a new document summarizing what is needed to meet WCAG 2.0 requirements within your website or application.
  • How do you implement media to be accessible for a variety of users? Tricks for writing better alternative texts, or when to provide an empty alt="" attribute, how to add video captions, or create transcripts are shared by Megan Zlock.

How to Create More Accessible Content
How to Create More Accessible Content, an article by Megan Zlock on how to deal with media in terms of accessibility. Worth reading.


CSS / Sass

Work & Life

  • After years of intensive analysis, Google has discovered that the key to good teamwork is being nice. Who would’ve thought that, but on the other hand, if Google needs years to get this right, other companies don’t know this either. Maybe it’s a chance to change it and finally treat everyone at work and at home nicely.
  • To be creative, you sometimes need to leave your desk behind. By the way, Zoran Jambor, author of CSS Weekly, started an inspiration newsletter.

And with that, I’ll close for this week. If you like what I write each week, please support me with a donation or share this resource with other people. You can learn more about the costs of the project here. It’s available via email, RSS and online.

Thanks and all the best, Anselm

Further Reading

Smashing Editorial (mrn)