cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lorin Beer <lorin.beer....@gmail.com>
Subject Re: Converting scripts to node
Date Fri, 12 Jul 2013 17:20:53 GMT
The primary benefit I see in moving to node based scripts is quality: it's
a lot easier to write and maintain complex scripts with good tests in js
than it is in bash. Even with the reliance on exiting command line tools
like adb.

It also makes contributing to the scripting side far less intimidating. A
Contributors may feel much more comfortable diving into a js node script
than a shell script.

On Fri, Jul 12, 2013 at 10:07 AM, Filip Maj <fil@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 <agrieve@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 <fil@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" <agrieve@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?
> >>>
> >>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message