Intriguing flow described by Tantek Çelik. I think fully offline is a fantastic goal, but I always fear that the practical problems of syncing algorithms get in the way (some changes simply aren’t mergeable).

I for years have been trying to find something to replace WordPress, which has turned into a tool that offers far more functionality than I actually need for my lowly blog, at the expense of making publishing far too complex. Static site generators are interesting (even if they sometimes seem over-engineered), but I really want something I can post to from multiple locations.

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.