Re: [Mesh] big

On 07/13/2013 06:44 PM, Mitar wrote: Meteor and big are very similar, in that they are both trying to make development of NodeJS apps that work on both the client and the server easier. i think the main difference is that the core of big is a resource manager (https://github.com/ahdinosaur/resource), and all additional functionality is provided through an ecosystem of independent, composable resources (https://github.com/ahdinosaur/resources) that define schemas of properties and methods. the benefit is more modularity, which should hopefully lower the entry bar to new open source developers, including to the point where non-programmers can easily make new object-like resources. to this end we are also focusing resources on reflection, where you take one resource (which has properties and methods), and then reflect it over multiple interface resources (such as html forms, command-line, web sockets, irc, rest api, documentation, package.json, twitter, email, ...), so that you can focus on your resource(s) and all the interfaces come for free. other benefits are that schemas are JSON-Schema and provide free validation and persistence, resources are CommonJS modules, methods have support for before and after hooks, and events are called every method call and can be used to call methods, and resource manager handles on-demand installation of each resource's npm dependencies. i hope some of above makes sense, if anyone wants to talk more you can find us on freenode in #big. we have yet to start on access controls and i haven't tested our node/mesh/replication system yet, but i will definitely keep your suggestion in mind as that would be the best case distributed app. cheers, dinosaur