Pony Foo Weekly

The web platform has many cynics and critics. The litany of complaints includes: incompetent developers (there’s nothing techies love more than being critical of other techies), bloated libraries, framework hell, recalcitrant browser makers, security nightmares, ever-changing specifications, and an unrelenting hype machine. All those criticisms have elements of truth. But there’s also an upside: web development is an open, decentralized, vibrant community, one which seems to inexorably stumble towards making better web applications at least possible.

And it also has open, welcoming subcultures that reject cool, detached cynicism and dominance displays. From projects like Nodeschool to the Recurse Center, there are thousands of people concerned with equipping more of us with the skills to build a better web. I associate Pony Foo with that same culture of learning & sharing. Started as a blog by Nicolás Bevacqua from Buenos Aires, Pony Foo has grown into a larger community that publishes in-depth articles about the web platform (i.e. the JavaScript language, HTML, CSS; various libraries, tools, and frameworks).

Given the rate of change in web development, such resources are indispensable for anyone who wants to do more than maintaining a legacy application. And Pony Foo helpfully provides a roundup of various findings from around the web (courses, tutorials, news, etc.), in a weekly email newsletter, which is just about the right frequency to not be overwhelmed.

While the newsletter highlights Pony Foo’s own articles, they are only a fraction of the content, and the biggest value-add is in the curation of resources from elsewhere. A typical example of a summary:

Error Handling in React 16

Dan explains how error handling works in React 16, which is out on public beta since yesterday. React 16 uses Fiber under the hood, although its async rendering capabilities aren’t turned on yet. It is expected this is enabled at some point in the React 16.x release line.

Dan Abramov

As the summary shows, occasionally the newsletter might benefit from some effort to make technical jargon more accessible or to provide a “why should I care” hook. But the headlines are easy enough to scan for stuff that seems relevant to you.

The newsletter does have sponsored posts in it, which are clearly marked. I don’t find them especially problematic and occasionally even useful. The content is under the Creative Commons CC-BY-NC-SA License, which is a bit restrictive (incompatible with Wikimedia projects, for example) but a lot better than conventional copyright. Whether you love or hate the web platform (or love-hate? :), if you regularly build upon it, I highly recommend subscribing (read a sample issue to see if it’s for you).