I tend to agree. The problem is certainly not acute enough to matter until sometime after 3 has settled. On 2013-07-13 5:08 PM, "Anis KADRI" <anis.ka...@gmail.com> wrote:
> I think I've voiced my opinion on this topic but I will state it again. I > (and I bet most people) do not like dependencies. You ask people to > download and install SDKs and that is already tedious enough. You now want > them to download an additional thing to make life easier for Cordova Core > Developers and not Cordova users which sounds backwards to me. > The argument that node is cross-platform and Windows is disregarded because > it does not use bash is not a valid one in my opinion. Platforms have to be > tested and you can't only rely on node's cross-platform support. The > introduction of node won't solve the testing aspect. > > 2 things would make me happy. > - Leave things the way they are (bash on *nix and cscript on windows). > - Use node but pre-package the dependency somehow so that users don't even > know that they are using node (I believe BlackBerry does that). > > > On Fri, Jul 12, 2013 at 10:40 AM, Filip Maj <f...@adobe.com> wrote: > > > I have to agree with Lorin on this one. Windows scripts are getting > > ignored and not maintained, no surprise. Moving to node won't eliminate > > windows neglect but should mitigate the issue of unix fixes not making > > their way into windows scripts. Don't think it's super high priority to > > get done soon, though. > > > > On 7/12/13 10:27 AM, "Brian LeRoux" <b...@brian.io> wrote: > > > > >So, science experiment. That's cool. [1] > > > > > >[1] https://twitter.com/jonathanpenn/status/355696329172844549 > > > > > > > > > > > >On Fri, Jul 12, 2013 at 10:07 AM, Filip Maj <f...@adobe.com> wrote: > > >> Main benefit here is abstracting away two scripts for *nix & > > >> windows-compatible platforms like android and blackberry. BB already > > >>uses > > >> node for those anyways.. > > >> > > >> On 7/12/13 9:47 AM, "Brian LeRoux" <b...@brian.io> wrote: > > >> > > >>>Most of the scripts themselves shell out to things like adb or > > >>>whatever so putting another layer of scripting abstraction over top > > >>>feels unnecessary (to me). I suppose the benefit is that on Android > > >>>we'd have less code? > > >>> > > >>>Are there other benefits? > > >>> > > >>> > > >>> > > >>>On Thu, Jul 11, 2013 at 6:55 PM, Andrew Grieve <agri...@chromium.org> > > >>>wrote: > > >>>> Cool! > > >>>> > > >>>> I don't think npm is a good idea for them since that will add > another > > >>>> avenue for mistakes to be made. Shelling out to them seems fine. You > > >>>>can > > >>>> also just require() them if you're sure they aren't going to mess up > > >>>>you're > > >>>> apps state (e.g. change your CWD), but shelling out is certainly > > >>>>safer. > > >>>> > > >>>> > > >>>> On Thu, Jul 11, 2013 at 6:24 PM, Filip Maj <f...@adobe.com> wrote: > > >>>> > > >>>>> Don't think for android specifically there has been any work on > this > > >>>>> > > >>>>> On 7/11/13 2:55 PM, "Andrew Grieve" <agri...@chromium.org> wrote: > > >>>>> > > >>>>> >We talked about unifying on node post 3.0 for our scripts (e.g. > > >>>>>android > > >>>>> >create script). > > >>>>> > > > >>>>> >Was wondering if anyone had started on this? > > >>>>> > > >>>>> > > >> > > > > >
