Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
The Reactive Manifesto (reactivemanifesto.org)
16 points by squidsoup on July 15, 2013 | hide | past | favorite | 2 comments


Right, because all the people who are in a positions to make decisions about writing event-driven code needed to do so was a manifesto.


I'm interested in the ideas presented here but wish the author had just written an article with practical examples of stacks that can facilitate this architecture. Presumably this is what tools such as core.async and channels in clojure are trying to solve. The fact that this is presented as a 'manifesto' without much in the way of practical advice seems a little bizarre. Given the ...err... 'signatories', this appears to be coming from the Typesafe guys, so where are the examples in scala?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: