First of all, thanks so much to everyone for generously providing their
thoughts. Very helpful and useful to me (and hopefully, others). Really
enjoying the node community culture.
In continuing to deepen my understanding, I would like to ask some follow
ups in regard to Isaac's points -- and my apologies in advance, as I know
these illustrate my basic lack of understanding...
On Monday, July 23, 2012 3:09:09 PM UTC-4, Isaac Schlueter wrote:
>
>
> Then we should do away with the package.json file for everything
> except publishing and stating dependencies, and make the development
> process more automatic; if you require('http') it should Just Work by
> fetching the http module that you need to use. (How to pick the right
> one if there are several updates? That is a bigass TBD. It's a lot
> of work.)
>
So I have basic familiarity with the package.json, and have created some
basic C++ add-in modules. However, I'm not clear on exactly what removing
everything but publishing and dependencies means....what kind of additional
features are in there that would be factored out? How does that lead to
making the development process 'more automatic'?
> For deployment, we should take shrinkwrap or "check in your deps" a
> step further, and have a way to create a static standalone bundle that
> can be deterministically unpacked and installed on a remote machine.
>
I'm not clear on exactly what you mean by a static standalone bundle.
Actually, to step back, I'm not sure you are referring to by 'check in your
deps' -- do you mean the fact that the node source code repo includes its
dependencies (v8 and uv) directly in the project? And as far as a
standalone bundle, are you talking about a different way of distributing
node itself, or rather modules created by 3rd party devs?
