Interesting deep dive into popular modern applications’ performance from a perspective of offline-availability, ownership and longevity, with a proposal for a new (to me) model, Conflict-free Replicated Data Types (CRDT).

I remain unconvinced that something like the hyper-collaborative experience of Google Docs can be replicated under anything except an always-online paradigm; on the other hand, I have yet to see that experience used productively – it’s a good demo, but not very useful in my eyes.

A List Apart’s From URL to Interactive series just concluded, and I think it’s worth a read for any web developer.

It’s structured in a way that reminds me of one of my favourite books, Charles Petzold‘s Code, moving from the bottom of the stack to the top.

An eBook by Addy Osmani on everything you could want to know, and then some, about the most efficient ways to serve images in browsers.

Jeremy Keith uses a discussion of the Angular JavaScript framework to set up the two (very broadly speaking) camps in web development: those who develop for the Web and those who develop on the Web. (I realise that speaking about them in those terms is biased, but I share Jeremy’s bias, so I’ll let it stand.)

This perfectly encapsulates discussions I’ve been having recently, and Jeremy’s way of putting it also helps me understand why others may feel this way and why they’re not necessarily wrong: Although I disagree, seeing the Web as a dumb pipe for your content is perfectly reasonable if one’s background is in non-Web development. If the Web is simply another platform, things such as RPCs and browser requirements are fair game.

But boy do I not share that sentiment.

Test cases for problematic uses of CSS