The "free" maintenance is a compelling reason to add node as a dependency.
I'll also flip and support this move but let's not focus on this just yet. Maybe file the issues and slate them for post-3.0. On 4/13/13 3:05 PM, "Jarrod Overson" <[email protected]> wrote: >Cordova may also gain extra hands and support in the process by switching >to node, or at least by adopting the stance that node is the 100% >supported >future. > >Grunt <http://gruntjs.com/> could also be appropriate as a task runner, >allowing shared tasks to be organized and distributed separately and to >leverage the community tasks <http://gruntjs.com/plugins> that already >exist. > >-- >Jarrod Overson >tw <https://twitter.com/jsoverson> | gh <http://github.com/jsoverson> >| g+<http://profiles.google.com/jsoverson> > | li <http://jarrodoverson.com/linkedin> > > >On Sat, Apr 13, 2013 at 12:49 PM, Simon MacDonald ><[email protected] >> wrote: > >> I used to be against requiring node to run the create scripts but I've >> reversed my position. >> >> I think it would be good to switch to node. Maintaining separate >> bash/jscript scripts is a pain in the ass and violates DRY. As well >>most of >> us don't even have PC's anymore so running the create script on Windows >>is >> not getting the attention it deserves. Check out the problems people >>are >> having on a Windows on our mailing list or on StackOverflow. >> >> Theoretically by moving to a node script should eliminate duplication >>and >> put everyone on a level playing field. >> >> >> Simon Mac Donald >> http://hi.im/simonmacdonald >> >>
