Release Date: 29 January 2016
It's the first sign of life since the last build in July 2015. I'm currently switching between Vim and Atom depending on the task and my mood, but seeing the development getting picked up again I might go back to Sublime Text instead of Atom. It just feels snappier.
(These updates happening on my birthday has to be a sign!)]]>
Chrome will be able to compress data up to 26 percent more than its existing compression engine, Zopfli, which is an impressive jump.
That's thanks to a new compression algorithm called Brotli, which is already in use in WOFF 2.0 web fonts.
The advantages are pretty significant, but Brotli is also available to HTTPS sites.
It looks like Firefox will also adopt the new algorithm. Let's hope it'll come to Safari, especially on mobile, too.
That's all nice and good but remember, that's not a free ticket to add unnecessary cruft to your sites.]]>
The problem with such a styleguide or patternlab is that it exists next to the real thing. When you change something in your code base you also have to update the particular code for the pattern in patternlab. To be honest I went very quickly from being excited to stop using it entirely. [...] But what if there was a way to combine the process of creating patterns, describing them and building your frontend. And what if your frontend was actually feeded by your patternlab. Yes yes yes, that's exactly why I never got around to using Patternlab. I missed the connection between my frontend components and the real website. Bastian built a simple Kirby plugin which does exactly that, it let's you create your frontend components and thus built a pattern library. But the exact code is also used on the real site.
It's just awesome to work which such a living pattern library.
I'm curious to try out Bastian's solution, which is probably a little bit more universally usable than ours.]]>
Before the refactor, my CSS weighed 111kb. After the refactor, it weighed 27kb.
That's a remarkable reduction!
I've used Harry Roberts ITCSS Methodology for a couple of projects too and it's my goto way these days, combined with BEM and some OOCSS and a few personal touches.
As Jordan mentions you are free to alter or abstract ITCSS how you want, but I have the feeling he gets the idea behind the objects and components layer kinda wrong.
Objects should be the layer without styling; the reusable, abstracted pieces you can almost always carry over from project to project. Components on the other hand are the styled building blocks of your site, which are different from project to project and it's therefore probably the layer with the most pieces.
Anyway, check out the talk by Harry Roberts and make up your own mind. It's awesome, even if you just take away some things from it.]]>
Don't feel inadequate if you aren't lining your nest with the shiniest, newest things possible. Who cares what technology you use, as long as it works, and both you and your users are happy with it? That's the beauty of new things: there's always a new one coming along. Don't let the pursuit of new, shiny things accidentally become your goal. Avoid becoming a magpie developer. Be selective in your pursuit of the shiny and new, and you may find yourself a better developer for it.
Still very true today.]]>
One of the projects I’ve been working on recently has been with a relatively new browser that I think is about to become big. The browser team at Samsung have been quietly building and evolving their own Chromium-based browser and I think it is about to play a big role in the evolution of the web.
Browser diversity is always good and it's especially good news when the stock browser of new Samsung Android devices is a modern and capable one. So let's watch this space and see what the future holds.]]>
The countless challenges raced through my mind as Gabe and I chatted—file size, performance, file size, image quality, file size, deadline. I could’ve walked away, but after brainstorming and talking through all the obstacles, I felt invested in the website—I wanted to be the one to make this special.
A very good, well written and entertaining Case Study.]]>
Progressive enhancement is a tool that will help you build faster, tougher sites. It is an investment in the strength and quality of your application. It will make your users happy because the app will still work, if imperfectly. It might just save you when disaster strikes, and if you’re interested in building the best websites possible, you should give it some thought.
It's not just about supporting non-JS users.]]>