In this post, I’ll outline some recent observations and approaches to delivering sites for speed and broader access, and link out to various tools we are using to facilitate our approach. All of the tips mentioned in this post are implemented on this very site, and we’ve tested them heavily to ensure that they’re working as well as they can.
Scott Jehl talks about all things performance in this article on the Filament Group blog. It’s a must read for every (Frontend) Web Developer. In project I’m currently working on I already used loadCSS and it’s awesome.
So I’ll put my own site under the microscope. I’m a seasoned RWD developer, I’ve worked on large projects, I co-host an award-winning front-end sound effects podcast, and I care about web performance; so my own blog should be a perfect use case.
Dave Rupert puts his own site under the microscope to find out how much page weight is generated by making his site function in a multi device world. At the end he goes on to see what he can do to further improve performance. Interesting read and probably something everybody should do sooner or later. At the least it’s a great learning experience.
The minimal-ui viewport property is no longer supported in iOS 8.
You can start to say your goodbyes to the controversial minimal-ui viewport property as it will be no longer supported in the upcoming iOS 8. After being a fan at first, I think it’s good that Apple is cancelling this feature.
At least for me it has led to a revival of my DIY past. Instead of spending time on something that might be sold or shut down tomorrow I much rather put on some safety goggles and build my own thing.
Bastian goes back to building stuff on his own. This post really resonates with me because I recently started to host and build more stuff for myself, too. For the first time I have a shared server, host my own git repositories, have my own image sharing service, and more. On the one hand it’s because I want to be independent and on the other hand it’s just fun.
If you’ve been following our Developer Tools series on the Mozilla Hacks blog, you’ve seen the developer tools evolve from pure inspection to a debugging environment both for web sites and apps on desktop and mobile. Today we want to introduce you to the next step of evolution: adding in-browser editing features across devices.
Working on Firefox OS apps? This is definitely for you. But it’s an interesting way in general. I tried a couple of times to develop inside Chrome DevTools but didn’t find it that good. But let’s see what’s coming.
Most of all, one would think that a company with $ 120 Million in funding and strong developer ties could come up with a better solution than shutting us down. Us, two guys building an App that many people preferred over their official one. Two guys willing to give that App away for free.
Soundcloud has shut down the amazing Soundflake. An app that was well designed, fast, easy to use and thus had everything the official Soundcloud iPhone app lacks. And the way Soundcloud handled it is just bad. BOOOO Soundcloud! (And I’m a big fan of the service)
The will-change property allows you to inform the browser ahead of time of what kinds of changes you are likely to make to an element, so that it can set up the appropriate optimizations before they’re needed, therefore avoiding a non-trivial start-up cost which can have a negative effect on the responsiveness of a page. The elements can be changed and rendered faster, and the page will be able to update snappily, resulting in a smoother experience.
This is a highly recommended article because it is very important that you fully understand the upcoming
will-change property before you use it. My biggest fear with this property is that it’ll get used with the intent of improving the performance of a site, but actually degrading it. So please take some time and read this article in full. It’ll be worth it.
No need for a fancy explanation. That’s what you get with a free CodePen account: a blog. You write stuff, you publish it, people read it. It’s absolutely that simple. But the tools are there to go nuts with it if you want to.
CodePen gets better and better. It’s so nice to see the service flourish. I use it everyday and am happy to support it in any way I can. Although I probably will blog on here instead of on CodePen. But for all the people who don’t have a blog but want to write about code, it’s the perfect place. Go nuts!
This document captures the use cases and requirements for standardizing a solution for “element queries.”
This is the Editor’s Draft for Element Queries from May, 30th, 2014. This is one of the most interesting and important topics for front end development after responsive images shipped in every major browser. Never heard of the term element query? Make sure to read this draft. It’s the future.
You want to contribute? Go ahead: https://github.com/responsiveimagescg/eq-usecases/
The Developer Channel provides a version of the browser for you to explore and test upcoming features and web standards support under development. Download this Channel to try out our new features before they are broadly available, and share your feedback with us to improve the product and let us know the features you need.
Microsoft coming out more in the open is really good news for everyone.
To be completely honest with you, I didn’t expect Ethan to reply to my email, let alone follow-through. I knew about Ethan – his skill, experience and sharp intellect – but what I didn’t know (and later found out), was simply how genuine and humble he is.
I met Ethan in Düsseldorf a few weeks back and this is exactly what I thought. Such a nice and humble guy.
I can only recommend listening to this Interview with him. Part 1 and Part 2 are out right now.
There is no express train to success. It’s years of taking the local, studying everything that rolls by your window. Trying to short circuit plain old hard work by job-hopping, artificially inflating yourself, taking shortcuts, or waxing poetic about subject matter you don’t know as much about as you think you do will come back to haunt you. Find some inspiration, put your head down, and get to work.
Pretty solid advice. Easy to nod your head in agreement, not always easy to actually do it. But it’s what I try to do every day.