Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Date: Wed, 18 Apr 2012 09:29:05 -0400
From: "Mark H. Wood" <mwood@IUPUI.Edu>
To: users@cocoon.apache.org
Subject: Re: Forms and maps
Message-ID: <20120418132905.GC4796@IUPUI.Edu>
References: <4F8EA6C2020000D40007A77A@pta-emo.csir.co.za>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-ripemd160;
	protocol="application/pgp-signature"; boundary="YD3LsXFS42OYHhNZ"
Content-Disposition: inline
In-Reply-To: <4F8EA6C2020000D40007A77A@pta-emo.csir.co.za>
User-Agent: Mutt/1.5.21 (2010-09-15)

--YD3LsXFS42OYHhNZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 18, 2012 at 11:34:26AM +0200, Derek Hohls wrote:
> It all depends on your environment and the "rate of change". There are
> many back-end systems (running on old but reliable technology) that
> hardly change at all.  However, the web (and now tablets/mobile) has a
> very high rate of change (and expectation of change).  The point here is
> that by using more loosely-coupled modules then you will only have to
> change the parts that really need to be changed; a monolithic approach
> is less amenable to that.

I think this may actually underscore the O.P.'s point.  Changing the
whole world in one go is the monolithic approach.  The modular
approach would enable choosing new mechanisms for new work and
sticking with old, established mechanisms for existing, still-useful
work when that makes sense.  Having to throw out piles of satisfactory
working code just to use a dependency version that still has the
attention of its maintainers is really unwelcome.

I think the complaint is that Cocoon 3 is really Butterfly 1.

--=20
Mark H. Wood, Lead System Programmer   mwood@IUPUI.Edu
Asking whether markets are efficient is like asking whether people are smar=
t.

--YD3LsXFS42OYHhNZ
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEAREDAAYFAk+OwaEACgkQs/NR4JuTKG8Q1ACeKaQ6G1v60Z2KxobjbXhPTTon
4gcAnjxuumyKwA4FnkVmkb2iEt/Dkmsz
=5xvF
-----END PGP SIGNATURE-----

--YD3LsXFS42OYHhNZ--