Mailing-List: contact users-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@buildr.apache.org
MIME-Version: 1.0
Sender: peter.j.donald@gmail.com
In-Reply-To: <586B429B-1669-4C7B-930F-497C6764D9A7@toulme.name>
References: <CADuAvzdL86BgBB=Pdq_E6WWp=9oinqauOn8Wn2iJ7GYrLTcERQ@mail.gmail.com>
 <CACiKNc7vhS5BK6se4HCqwkX-Y7OL3hESibBmSmCaBivS1ONLsw@mail.gmail.com> <586B429B-1669-4C7B-930F-497C6764D9A7@toulme.name>
From: Peter Donald <peter@realityforge.org>
Date: Thu, 13 Oct 2016 08:39:37 +1100
Message-ID: <CACiKNc5P2xtVgQYp-+kx=SAHa+_H0Nn+1PrZGZ633VOzf=vOvQ@mail.gmail.com>
Subject: Re: Dependencies are naturally version ranges, not single versions
To: users@buildr.apache.org
Content-Type: multipart/alternative; boundary=94eb2c0c9bbe6eac4c053eb1d4d4
archived-at: Wed, 12 Oct 2016 21:39:44 -0000

--94eb2c0c9bbe6eac4c053eb1d4d4
Content-Type: text/plain; charset=UTF-8

On Wed, Oct 12, 2016 at 7:02 PM, Antoine Toulme <antoine@toulme.name> wrote:

> For some reason, the JS community seems to prefer just trusting that new
> versions won't break anything. Its either very brave of them really (or
> maybe just foolish).
>

I think there is a few features that distinguish the js community wrt
libraries.

* The libraries are untyped so don't fail to compile if something changes,
only fail at runtime if actually use the feature that changed.
* They have had semver integrated into their community at least in theory
from very early on where in java or ruby it tends to be up to each
community to follow or not.
* Their tools have supported semver from the beginning.
* Their libraries are usually much smaller, and people often write new ones
rather than reuse.
* The ecosystem has not really stabilized so if you are not constantly
updating you are probably running into other issues ;)

That said - I still much prefer fixed versions for stability, particularly
if you have to support it over many years.

-- 
Cheers,

Peter Donald

--94eb2c0c9bbe6eac4c053eb1d4d4--