hope you’re all doing fine and had a great week. After last weeks massive input in WebDevLand this week is a bit calmer. But don’t worry, you’ll always get a few articles from me. This week I have IE news, free HipChat, the importance of listening, Fira font, performance budgeting, a better
console.log() and element queries for you. Have fun reading it!
- HipChat is now free for normal users and teams including one to one chat as well as group chats. To get video chat and unlimited history, it’s still $2/user/month.
- The Internet Explorer team announced the next version of IE, including Web Audio API, Media Capture API, ES6 Promises, HTTP/2, and some other cool features. Along with that,
status.modern.ieis now Open Source.
- Sometimes we should rather be silent and listen instead of always sharing our own thoughts which might be wrong anyway. A good read on world-problems, minorities and gender discussions.
- Fira font, Firefox OS’ typeface, is now available in version 3.1 and free to download.
- A deeper look in automating CSS Sprites for large organisations by the people of Booking.com.
- Git 2.0 has been announced. For news and changes, just read the linked mail—it covers everything.
- Tim Kadlec on Performance Budgeting with Grunt, introducing the tool
grunt-perfbudgetthat sets up private WebPerfTest.com instances for your project.
- Many of us talk constantly about web performance but then, on the other hand, they use link shorteners everywhere (okay, mostly on Twitter). have you ever considered how harmful Link shortners are performance-wise?
HTML / SVG
- A brand new slidedeck by Sara Soueidan who held a great talk about SVG at CSSConf in Florida this week.
console.log()deliver a better output with script, line and char number.
- Promises are easier to understand and read.
- Data Binding Revolutions with
Array.observe(), coming to ES7 and shipping in Chrome 36 beta.
- Socket.IO 1.0 is out with a new engine, automated testing, better debugging and much more.
- Ben Frain asks if we do wrong using multiple classes for UI components. Because what else for do we have
[class=^"btn"]and other cool selectors?
- Do we need Element Queries? If you think so, please let us know about your use cases.
- Writing modular CSS by approaching the Single Responsibility Principle.
- Great effects to introduce your online articles…
To support this project, Flattr or gratipay me or share this resource with other people.
Thanks and all the best,