To install any plugins you at least need plugman which requires node. Our users are most likely going to have to install node as a dependency at some point. I don't see why having it as a dependency for platform libraries is such a big deal.
On Wed, Aug 7, 2013 at 11:34 AM, M. Lantz <mattla...@gmail.com> wrote: > +1 > > Agreed I pretty much only use Cordova cli at this stage to make apps and > as such don't have any issues keeping my node up to date or relying on is > as a dependency. > > M. Lantz > > On 2013-08-07, at 1:07 PM, Frank Hennig <fhe.developm...@gmail.com> wrote: > > > +1 for all platforms > > > > I think it's not really an completely new dependency. Some components > actually depends on node.js like cordova-cli and plugman. Many developers > of cordova app's actually using grunt or bower and other node related stuff > to lint or to test their html and js code. > > > > A consistent tool and script language it's easier to maintain an to > debug. > > > > > > On Aug 7, 2013, at 12:14 AM, Filip Maj wrote: > > > >> I would like to introduce node.js as a dependency for the platform > >> libraries, so that the platform scripts (bin/create, cordova/run, etc) > are > >> written in node. > >> > >> Pros: > >> - For multi-OS platforms (Android, BlackBerry), this reduces committer > >> cognitive load as the scripts do not need to be authored in two > different > >> script languages (I.e. Shell for unix-y Oses, Wscript for Windows) > >> - consistency in tool/script language. Cordova-js, coho, cli and plugman > >> are all written on top of node.js. > >> > >> Cons: > >> - Introducing a new dependency > >> > >> NB: This is separate from platform-spec; I would like to see > platform-spec > >> created/used regardless of the outcome of this thread. > > >
