Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F3F7FD4A4 for ; Thu, 1 Nov 2012 16:01:15 +0000 (UTC) Received: (qmail 88672 invoked by uid 500); 1 Nov 2012 16:01:15 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 88457 invoked by uid 500); 1 Nov 2012 16:01:14 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 88428 invoked by uid 99); 1 Nov 2012 16:01:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 16:01:13 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chewbranca@gmail.com designates 209.85.220.52 as permitted sender) Received: from [209.85.220.52] (HELO mail-pa0-f52.google.com) (209.85.220.52) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 16:01:08 +0000 Received: by mail-pa0-f52.google.com with SMTP id hz10so1753627pad.11 for ; Thu, 01 Nov 2012 09:00:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=5XrzqNuNgEPK6HjGh6QHhZ9HT51amP1JDHzDGalcOQY=; b=resK1Jgiy+w+9PdoCqH8GTFLXpIklqIHYZsFWxo97A0g/YEC6wboONJrpS32BVmhKR 9mRYvUvI03QSi5molrfaX20SYpOCaXY9/uGTzrnGEJNBYIKPWyyUaZVGwIHQ73vi4qah tyaQx6yGWBhLdst0/NI1dj2rEXNG5k0vHc4TIAKHUiXWxA/N3iy1yae/KDLfG9OcHdHI UxDhdOQKU/PZewfsylSsqQ+T146xeQyG1TdduK2/MBkqhDByhL7ppwb3uZNkq9YyPPF2 cqf0JkuyHNfVdK+1CVZs72Tpc7eFoP6EgNusledUt7CFTdpvb75ErMO55AtvY+GpTHPz loTw== MIME-Version: 1.0 Received: by 10.68.224.69 with SMTP id ra5mr123160950pbc.114.1351785648602; Thu, 01 Nov 2012 09:00:48 -0700 (PDT) Received: by 10.66.190.100 with HTTP; Thu, 1 Nov 2012 09:00:48 -0700 (PDT) In-Reply-To: References: <4679D8A1A1BF4B16B584949A73A4FBD7@cloudant.com> Date: Thu, 1 Nov 2012 09:00:48 -0700 Message-ID: Subject: Re: Futon.Next Proof of Concept From: Russell Branca To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I understand your apprehension, however, the primary ways of minifying javascript these days is with a javascript lib, or with a java lib. It should be noted that the node.js dependency is strictly as a build tool, and not actually required for building couchdb. We could make it an optional dependency, and just have a default compiled version in the codebase at all times, allowing you to skip the node.js dependency if you just want the standard configuration. For a vanilla couchdb install, there shouldn't actually be any changes necessary to the compiled app, so this could be a reasonable approach. -Russell On Thu, Nov 1, 2012 at 4:49 AM, Robert Newson wrote: > Needing node.js to build couchdb? I hate that. > > > On 1 November 2012 11:46, Simon Metson wrote: > >> Hi, >> >> >> On Thursday, 1 November 2012 at 11:35, Alexander Shorin wrote: >> >> > Because it's additional semi justified dependencies and whole project >> > goes far away from couchapp concept, imho. >> >> I don't think it does. In fact I'd say it emphasises the flexibility of >> couch apps and how they play nicely with other tools ("hey look, you can >> use this database with the toolset I'm used to from jquery"). >> > If Erica will be bundled tool out of CouchDB box, better to dance around >> him. >> >> I'd rather use something that exists today and evaluate erica when it is >> included with CouchDB and has the necessary feature set in the future. >> >> With grunt we can get consistent build environments, with erica we'd >> either have people installing tools (linters, less compiler, minify-ers >> etc) manually/ad-hoc, have to rely on something like npm (and if we're >> doing that, why not use grunt?) or build it ourselves (eurgh!). >> >> Cheers >> Simon >> >>