The Reactive Manifesto

I”ve lately been investigating Play Framework (https://www.playframework.com/), which is both an interesting and good project and community. Typesafe holds copyright over the open source (ASL2) code and maintains itself as the final arbiter of code decisions. But they emphasise that they value community perhaps even more than the code itself; nice. (It reminds me of Apache–which makes me think: What company doesn’t espouse that view? I mean, besides one of my previous employers.)

The Play Framework community pages are pretty good, but see for yourself. (https://www.playframework.com/community-process) They are models of clarity. (We’ve gone a long way since those early days when website documentation was better left unwritten, as it was often so confounding.) But I was especially pleased by their direct reference to the Reactive Manifesto, cited below. Actually, I love this continuing (if slightly less vigorous) age of the manifesto; so much like fin-de-siècle art, and for a reason. And although I hear increasing calls to “make it new” again, these, as with Pound’s original exhortation, come from the right. (Pound meant, as do these neocons, to grab the old before it fades into icky future and vivify it. Of course, I tend to think of such efforts as vampiric and believe it better to leave the undead where they lie than to pretend that the best solution for the future is the past again.) The Reactive Manifesto powerfully resonates with what I and others have been advocating for some time now–but read it.

via The Reactive Manifesto.