The slides are from a talk I did at the MunichJS meetup. It contains some background ideas on how I changed from blogging about "philosophical" ideas (and Ruby) to blogging about JavaScript. Parts of my blog actually resulted into the book on fullstack JavaScript development with Backbone, see http://pipefishbook.com/
hm.. the gist seems offline now?
The background of the gist was using: Browserify as service http://wzrd.in/ and some examples how to bind browserify modules to make require('foo') work in the developer console.
Thanks for pointing these things out! Indeed, there are some similar projects/approaches, e.g. https://www.arangodb.org/foxx and https://github.com/brainyio but so far, most RESTful APIs out-of-the-box solutions have some rough edges.
That might be true. It would be interesting to have some ways to track quality of Node modules, maybe in terms of open issues, last commit, or maintainer activities.
nice - most examples I've seen already elsewhere. One thing that confuses me still slightly is the difference between "state" and "property" of a component. Anyone has an example that shows the difference? E.g. when the item in the navigation is selected, is that a state or a property?